NView NNM (V5) Installation Guide (Rel 43) - DAVANTEL NNM (V5) Installation Guide (Rel_43).pdf ·...

NView NNM (V5)

Installation Guide

(Rel_43)

www.raisecom.com

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: [email protected]

Address: Building 2, No. 28, Shangdi 6th Street, Haidian District, Beijing, P.R.China

Postal code: 100085

-----------------------------------------------------------------------------------------------------------------------------------------

Notice

Copyright © 2014

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 (V5) Installation Guide Preface

Raisecom Technology Co., Ltd. i

Preface

Objectives This guide describes methods, steps, and precautions for installing the NView NNM system.

It helps you install the NView NNM system properly.

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.

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.

Raisecom


Raisecom Technology Co., Ltd. ii

General conventions

Convention Description

Times New Roman Normal paragraphs are in Times New 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.

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.

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.

Raisecom


Raisecom Technology Co., Ltd. iii

Change history Updates between document versions are cumulative. Therefore, the latest document version

contains all updates made to previous versions.

Issue 43 (2013-09-01)

Fourth commercial release

Added communication bandwidth requirements, suitable for communication bandwidth

between the NMS Server and NMS Client, and between the distributed master server and

distributed slave server.

Added contents about deploying the NMS Client.

Updated descriptions about the installation procedure of the NView NNM system (kernel

version V5.4.1) based on the installation program of the NView NNM system (kernel

version V5.4.1).

Updated interface requirements of the NView NNM system.

Issue 42 (2013-06-01)

Third commercial release

Added descriptions about the installation procedure of performance distributed

deployment based on the installation program of the NView NNM system (kernel

version V5.4.1).

Updated descriptions about the installation procedure of the NView NNM system (kernel

version V5.4.1) based on the installation program of the NView NNM system (kernel

version V5.4.1).

Issue 41 (2012-09-01)

Second commercial release

Added descriptions about cases where the License is not compatible with the NView

NNM system version.

Updated descriptions about the installation procedure of the Nview NNM system (kernel

version V5.4.1). The installation steps are identical to the ones of the NView NNM

system (kernel version V5.4).

Issue 40 (2012-06-01)

Initial commercial release

Raisecom

NView NNM (V5) Installation Guide Contents

Raisecom Technology Co., Ltd. iv

Contents

1 Preparing for configurations ....................................................................................................... 1

1.1 Overview .......................................................................................................................................................... 1

1.2 System deployment .......................................................................................................................................... 5

1.2.1 Introduction to system program .............................................................................................................. 5

1.2.2 Selecting deployment mode .................................................................................................................... 7

1.2.3 Deployment modes of NMS Clients ....................................................................................................... 7

1.3 Operating environment requirements ............................................................................................................. 12

1.3.1 Hardware environment requirements .................................................................................................... 12

1.3.2 Operation system requirements ............................................................................................................. 14

1.3.3 Interface requirements ........................................................................................................................... 16

1.3.4 Bandwidth requirements ....................................................................................................................... 18

1.3.5 Other requirements ................................................................................................................................ 18

1.4 Confirming installation procedures ................................................................................................................ 19

2 Installation steps ......................................................................................................................... 20

2.1 Installing NView NNM system ...................................................................................................................... 20

2.2 Installing NMS Client .................................................................................................................................... 27

2.3 Installing distributed PM service .................................................................................................................... 30

2.4 Upgrading NView NNM system .................................................................................................................... 31

3 Starting configurations .............................................................................................................. 33

3.1 Configuring NView NNM to be started automatically with operation system ............................................... 33

3.2 Configuring services to be started automatically with NView NNM system ................................................. 33

4 Modifying and removing NView NNM system ................................................................... 35

4.1 Modifying NView NNM installation program ............................................................................................... 35

4.2 Removing NView NNM system ..................................................................................................................... 36

5 FAQ ................................................................................................................................................ 40

5.1 How to stop SNMP Trap service of Windows operation system? .................................................................. 40

5.2 Why does NView NNM system fail to receive alarms sent by NEs? ............................................................. 40

5.3 Why do distributed NMS Clients fail to connect to NMS Server? ................................................................. 41

5.4 Why does NMS Server fail to connect to database when being started? ........................................................ 42

5.5 Why does system prompt communication timeout or SNMP operation failure when EMS is being started? 42

Raisecom

NView NNM (V5) Installation Guide Contents

Raisecom Technology Co., Ltd. v

5.6 How to eliminate scrambled characters when the NView NNM system is installed for a non-Einglish system?

.............................................................................................................................................................................. 42

5.7 Why does the InstanceServer service fail to be started with an "Unable to load JMV" prompt box being

displayed? ............................................................................................................................................................. 44

6 Appendix ...................................................................................................................................... 47

6.1 Terms .............................................................................................................................................................. 47

6.2 Abbreviations ................................................................................................................................................. 49

Raisecom

NView NNM (V5) Installation Guide Figures

Raisecom Technology Co., Ltd. vi

Figures

Figure 1-1 Centralized deployment ........................................................................................................................ 2

Figure 1-2 Performance-distributed deployment .................................................................................................... 3

Figure 1-3 NMS Server and NMS Clients at the same network............................................................................. 8

Figure 1-4 NAT network environment ................................................................................................................... 9

Figure 1-5 Dual-NIC network environment ........................................................................................................... 9

Figure 1-6 Modifying the System.properties configuration file (1) ..................................................................... 10

Figure 1-7 Modifying the NMS_Services.xml configuration file (1) ................................................................... 10

Figure 1-8 Deploying NMS Clients in dual-NIC environment ............................................................................ 11

Figure 1-9 Modifying the System.properties configuration file (2) ..................................................................... 12

Figure 1-10 Modifying the NMS_Services.xml configuration file (2) ................................................................. 12

Figure 2-1 License agreement .............................................................................................................................. 21

Figure 2-2 Selecting components to be installed .................................................................................................. 22

Figure 2-3 Selecting the License file .................................................................................................................... 23

Figure 2-4 Selecting the IP address of the NMS Server ....................................................................................... 24

Figure 2-5 Installation mode of MySQL database ............................................................................................... 24

Figure 2-6 Confirming installation information ................................................................................................... 25

Figure 2-7 Installation file .................................................................................................................................... 26

Figure 2-8 Installing the NView NNM system completely .................................................................................. 26

Figure 2-9 Start menu (1) ..................................................................................................................................... 27

Figure 2-10 Start menu (2) ................................................................................................................................... 29



Figure 2-13 Upgrading the NView NNM system successfully ............................................................................ 32

Figure 4-1 Modifying the NView NNM installation program.............................................................................. 36

Figure 4-2 Menus for removing the NView NNM system ................................................................................... 37

Figure 4-3 Removing the NView NNM system through the Control Panel ......................................................... 37

Raisecom

NView NNM (V5) Installation Guide Figures

Raisecom Technology Co., Ltd. vii

Figure 4-4 Removing the NView NNM system ................................................................................................... 38

Figure 4-5 Confirming the removal operation ...................................................................................................... 38

Figure 4-6 Prompting to restart the PC ................................................................................................................ 39

Figure 5-1 Prompt box (1) .................................................................................................................................... 44

Figure 5-2 Prompt box (2) .................................................................................................................................... 45

Raisecom

NView NNM (V5) Installation Guide Tables

Raisecom Technology Co., Ltd. viii

Tables

Table 1-1 Hardware configurations of the PC (1) ................................................................................................ 13



Table 1-4 Supported operation systems ................................................................................................................ 14

Table 1-5 Requirements on user privileges of operation system .......................................................................... 15

Table 1-6 Interface requirements .......................................................................................................................... 16

Table 1-7 Preparing files ...................................................................................................................................... 19

Table 2-1 Functions of PCs and installation components ..................................................................................... 21

Raisecom

NView NNM (V5) Installation Guide 1 Preparing for configurations

Raisecom Technology Co., Ltd.

1

1 Preparing for configurations

The chapter describe features and preparatory work to be learned before installing the NView

NNM system, including the following sections:

Overview

System deployment

Operating environment requirements

Confirming installation procedures

1.1 Overview Raisecom upgrades the NView NNM system from kernel version V5.4 to V kernel version

5.4.1. Kernel version V5.4.1 covers all features of kernel version V5.4, updates topology

management, security management, and alarm management, and integrates abundant Element

Management System (EMS) software. Compared with the older version, the new version is

easier of use.

The NView NNM system (kernel version V5.4.1) provides matching installation program and EMS versions. After installing the NView NNM system (kernel version V5.4.1), you need to use the matching EMS upgrade packet to upgrade the EMS.

Installation and deployment modes of NMS Server

The NMS server supports centralized deployment and performance-distributed deployment

mode. In this 2 deployment modes, only one NMS Server can be installed. In addition, you

can use the NMS Control to manage services of the NView NNM system.

Centralized deployment: all service programs of the NView NNM system are installed

on the same server where the NMS server is installed. In general, this mode is applied.

Figure 1-1 shows the typical networking application of centralized deployment.

Raisecom



2

Figure 1-1 Centralized deployment

Performance-distributed deployment: the PM service of the NView NNM system can be

installed independently. This helps to reduce resources requirements of the NMS Server.

Figure 1-2 shows the typical networking application of performance-distributed

deployment. The PM service and other NView NNM services are installed on different

PCs. This helps to share the hardware processing pressure of the NMS server and

improve the performance and efficiency of the NMS Server.

Performance-distributed deployment mode is not required if you do not need to monitor the performance data. During installation, the PM service is installed on the NMS Server and independent PM server simultaneously. However, you can enable PM service from the PM server only.

Raisecom



3

Figure 1-2 Performance-distributed deployment

At present, centralized deployment mode is adopted for installing the NView NNM system (kernel version V5.4.1). NMS Clients can be installed on different PCs. To deploy PM service independently, you can install the PM program in performance-distributed deployment mode.

Installation and deployment modes of NMS Clients

In either of the 2 deployment modes, the NMS Clients can be installed on multiple PCs. Each

NMS Client can connect to the NMS Server for managing devices at different physical

positions. In addition, by creating different accounts and operation privileges, you can realize

hierarchical, privilege-based, and domain-based maintenance mode.

Descriptions about installation files

To install the NView NNM system (kernel version V5), you need to use the installation

program (kernel version V5.4.1) and the matching upgrade packet. For details, see NView

NNM (V5) Upgrade Guide.

The License file used by the NView NNM system must be matched with the specified NView NNM system version and EMS version. Before installing and upgrading the NView NNM system, verify that the License file is matched with the software and that the new License file is available.

Raisecom



4

The installation program of the NView NNM system adopts a wizard design. You can select

installation components as required and then click buttons step by step until finishing the

operation. Chapter 2 describes how to install the NView NNM system, which fits for users

who deploy the NView NNM system initially. For details about how to upgrade the installed

NView NNM system, see NView NNM (V5) Upgrade Guide.

The installation files include the following types:

Installation program of the NView NNM system: include the NMS Server, PM service,

and NMS Client.

– Be grouped into 32-bit and 64-bit installation programs: related to 32-bit and 64-bit

architecture and operation systems.

– The file name is set to NView_NNM_V5_timestamp_operation system type.

– For example, for the file name NView_NNM_V5_20130409_win32.exe, the

NView_NNM_V5 indicates the NView NNM system; the 20130409 indicates that

the timestamp is set to April 9, 2013; the win32 indicates that the installation system

fits for 32-bit Windows operation system.

Installation program of the NMS Client: include the NMS Client only.

– Be grouped into 32-bit and 64-bit installation programs: related to 32-bit and 64-bit

architecture and operation systems.

– The file name is set to NView_NNM_V5_Client_timestamp_operation system type.

– For example, for the file name NView_NNM_V5_Client_20130409_win64.exe, the

NView_NNM_V5_Client indicates the NMS Client; the 20130409 indicates that the

timestamp is set to April 9, 2013; the win64 indicates that the installation system fits

for 64-bit Windows operation system.

Changes of installation features

Compared with the previous versions, the installation program (kernel version V5.4.1)

changes the following features:

Support independent NMS Server installation program. You can select one or more

installation programs of the NMS Server, PM service, and NMS Client.

Support configuring the IP address translated through Network Address Translation

(NAT) protocol. This helps NMS Client at the public network to access the NMS server

at the private network. In this case, the NMS Client needs to access the translated IP

address of the NMS server.

Support independent NMS Client installation program to install the NMS Client only.

Add installation programs used for the 64-bit architecture and operation system.

Support installation programs for 32-bit and 64-bit NMS Server and NMS Client. You

can select the installation programs based on the PC architecture and operation system.

You must select the installation program based on the architecture and operation system of the PC. The architecture and operation system must be matched. The 32-/64-bit architecture should be installed with 32-/b4-bit operation system. Otherwise, installation fails. When the NView NNM system is running, the NMS Client can access 32-/64-bit NMS Serve and can be upgraded through the 32-/64-bit NMS Server regardless of whether the NMS Client is a 32-/64-bit one.

Raisecom



5

1.2 System deployment When deploy the NView NNM system, consider the size of the managed network. In a large

network, requirements on the server and database are higher. In general, the server

configurations are based on the number of equivalent Network Elements (NEs). For

calculation method of equivalent NE, see NView NNM (V5) Product Description or contact

the Raisecom support engineers for help.

1.2.1 Introduction to system program

The NView NNM system adopts the Client/Server (C/S) architecture. One NMS Server can

be connected with multiple NMS Clients for network management.

At present, the NView NNM system program includes the following items:

NMS Server program (including the database)

NMS Client program

PM service program

Upgrade program

NMS OMT program

NMS Server program

The NMS Server is the kernel of the NView NNM system. In general, it is installed on a

server with better hardware configurations.

The NMS Server provides the following functions:

As the management server, exchange the polling information with the device.

Receive information or alarm sent by the device.

Reply configuration and data query requests of the NMS Client.

Process various operations logically.

Support hierarchical, privilege-based, and domain-based security management.

Support system monitoring.

Support PM service.

Support data center.

Support data dump.

Support connecting with the upper NMS through the northbound interface.

Verity the legality of the software and control the number of manageable nodes through

the License manager.

NView NNM database

The database adopts the MySQL database management system and is a key component of the

NView NNM system. In general, it is installed on a server with better hardware configurations

and larger capacity. The database saves the network topology information, alarm information,

inventory information, performance information, customer information, engineering

information, and various logs.

Raisecom



6

You do not need to install and upgrade the MySQL database program independently. It can be installed and upgraded through the matching NView NNM installation program and upgrade packet.

NMS Client program

The NMS Client is the Graphical User Interface (GUI) of the NView NNM system. In general,

it is installed on a PC for monitoring the network. The NMS Client is responsible for sending

requests and displaying information. With multiple NMS Clients, you can realize hierarchical,

privilege-based, and domain-based configuration and management mode. In addition, you can

monitor multiple physical locations simultaneously.

NView NNM PM service program

The NView NNM PM service program provides performance management for the NView

NNM system. It supports monitoring performance data of the whole network based on the one

of the NE. The NView NNM PM service program can help the administrator learn the load

and traffic of the network at present and during the past. It provides evidence for pre-warning

the network failure, troubleshooting the problems, and optimizing the network.

The PM service that matches with the NView NNM system (kernel version V5.4.1) replaces the original one (before kernel version V5.4). Therefore, the original performance service and performance probe programs are replaced by the PM service program. In centralized deployment mode, the PM service (kernel version V5.4.1) will

replace the original performance program and be deployed with the NMS Server together.

In performance-distributed deployment mode, the PM service can be deployed on the PC where the original performance program is installed.

NView NNM upgrade tool

The NView NNM upgrade tool is used to upgrade, back up, and roll back of the NView NNM

system. It provides convenient operation and maintenance for upgrading the NView NNM

system smoothly, better meeting requirements on maintenance and operation management.

The NView NNM upgrade tool is installed and upgraded with the NMS Server, PM service,

and NMS Client together.

NMS OMT

The NMS OMT detects the NView NNM system and the PC where the NView NNM system

is installed to find problems and troubleshooting them, ensuring proper operation of the

NView NNM system. It supports the following functions:

Provide automatized solutions for locating, analyzing, and resolving faults during the

operation and maintenance period.

Enhance performance of the NView NNM system when the system is running.

Raisecom



7

Help the administrator to learn the operating status, device management capability, and

service management capability of the NView NNM system in advance.

The NMS OMT is installed and upgraded with the NMS Server together.

Follow-up upgrade of NMS Server

To perform follow-up upgrade on the NMS Server, you just need to perform the upgrade

operation on the PC where the NView NNM system is installed. All programs installed on the

PC will be upgraded.

Follow-up upgrade of PM service in performance-distributed deployment mode

After the NMS Server is upgraded successfully and the network management server of the

NMS Control is started, the PM service will connect to the upgraded NMS Server and be

upgraded automatically.

In addition, you can use the upgrade tool and upgrade packet to manually upgrade the PM

service in performance-distributed deployment mode.

Follow-up upgrade of NMS Client

After the NMS Server is upgraded successfully, when the NMS Client is being started, it will

connect to the upgraded NMS Server and be upgraded automatically.

In addition, you can use the upgrade tool and upgrade packet to manually upgrade the NMS

Client.

1.2.2 Selecting deployment mode

The deployment modes of the NView NNM (kernel version V5.4.1) system include the

centralized deployment mode and performance-distributed deployment mode.

Centralized deployment: the NMS Server is installed on a server. This deployment mode

is suitable for small network.

Performance-distributed deployment mode: deploy NMS Server and PM service on

different servers. This deployment mode is suitable for large network.

You can select a deployment mode as required. You can implement the above deployment

modes by selecting different installation interfaces during installation.

1.2.3 Deployment modes of NMS Clients

The NMS Clients can be installed on multiple PCs for network management at different

locations. In addition, by creating different accounts and operation privileges, you can realize

hierarchical, privilege-based, and domain-based maintenance mode.

Centralized deployment mode: the NMS Client and NMS Server are installed on the

same PC. In this mode, the NMS Client and NMS Server run simultaneously. Therefore,

it brings higher requirements on the PC.

Distributed deployment mode: the NMS Client and NMS Server are installed on

different PCs. In this mode, it brings lower requirements on PCs because the NMS Client

and NMS Server run on different PCs. In addition, it facilitates managing the network at

different locations.

Raisecom



8

Networking environment of distributed deployment

When deploying the NMS Clients in distributed mode, note the network environment between

the NMS Clients and NMS Server.

If the NMS Server and NMS Clients are at the same network, they can access each other

and the NMS Server can manage the NMS Clients, as show in Figure 1-3.

If the NMS Server and NMS Clients use the IP address translated by the NAT protocol to

establish connection, you need to enter the public IP address of the NMS Server when

installing the NMS Server, as shown in Figure 1-4. The public IP address of the NMS

Server is the one translated through the NAT protocol.

If the NMS Server uses dual Network Interface Cards (NICs), you need to enter the

public IP address of the NMS Server when installing the NMS Server, as shown in

Figure 1-5. One NIC is connected to the NE through the IP address of the intranet and

the other NIC is connected to the NMS Clients through the IP address of the extranet.

The NMS Clients are connected to the IP address of the public NIC of the NMS Server.

Figure 1-3 NMS Server and NMS Clients at the same network

Raisecom



9

Figure 1-4 NAT network environment

Figure 1-5 Dual-NIC network environment

Modifying configuration parameters of NAT/dual-NIC environment

When deploying the NMS Clients in distributed mode, in NAT/dual-NIC network

environment, modify the configuration parameters in the following cases:

NAT-translated IP address of the NMS Server is changed.

Public IP address of the dual NIC NMS Server is changed.

Raisecom



10

Do not configure the public IP address of the NMS Server when installing the NMS

Server.

Step 1 Stop all programs of the NView NNM system.

Step 2 Stop the operation system service of the NMS Server. Choose Start > Control Panel >

Administrative Tools > Services, right-click the NMSServer record and then choose Stop

from the right-click menu.

Step 3 Modify the OuterIP parameter of the System.properties configuration file at the NMS Server

and NMS Client.

Open the System.properties configuration file through the text document. By default, it is

saved at C:\NMS\PLATFORM\NNM5\globalconfig\System.properties.

Set the OuterIP parameter to the NAT-translated IP address of the NMS Server or the

public IP address of the dual-NIC NMS Server. For example, if the public IP address of

the NMS Server is changed to 1.2.3.4, the OuterIP parameter is set to 1.2.3.4, as shown

in Figure 1-6.

Save and close the configuration file.

Figure 1-6 Modifying the System.properties configuration file (1)

Step 4 Modify the ServiceComponent parameter of the NMS_Service.xml configuration file at the

NMS Server.

Open the NMS_Services.xml configuration file through the text document. By default, it

is saved at C:\ NMS\PLATFORM\NNM5\server\config\NMS_Services.xml.

Modify the ServiceComponent parameter and add the OuterIP parameter. For example, if

the public IP address of the NMS Server is changed to 1.2.3.4, the added OuterIP

parameter is set to 1.2.3.4, as shown in Figure 1-7.


Figure 1-7 Modifying the NMS_Services.xml configuration file (1)

Step 5 Start the NView NNM system.

Examples for deploying NMS Clients in dual-NIC environment

As shown in Figure 1-8, NMS Clients are deployed. NMS Client 1 and NMS Client2 can

access the NMS Server.

Add NMS Client 1 connected to the extranet. Because you do not enter the public IP

address of the NMS Server when installing the NMS Server and enter the IP address of

the NIC connected to network B when installing NMS Client 1, you need to modify the

configuration file of the NMS Server and NMS Client 1.

Raisecom



11

The original NMS Client (NMS Client 2) and the NMS Server are at the network B

(intranet) and they can communicate properly.

The NMS Server is installed on a PC with 2 NICs.

The 2 NICs are configured with IP addresses of network A and network B.

– IP address of NIC A is set to 10.0.0.1 and the mask is set to 255.0.0.0.

– IP address of NIC B is set to 20.0.0.1 and the mask is set to 255.0.0.0. It means

selecting the IP address of the NMS server when you install the NMS Server.

NMS Client 1 is in network A. The IP address is set to 10.0.0.2 and the mask is set to

255.0.0.0. Because NMS Client 1 is in network A (extranet), you need to modify the

configuration file of NMS Client 1.

NMS Client 2 is in network B. The IP address is set to 20.0.0.2 and the mask is set to

255.0.0.0. Because NMS Client 2 is in network B, it can access the NMS Server without

being configured.

Figure 1-8 Deploying NMS Clients in dual-NIC environment

Step 1 Stop all NMS Client programs.

Step 2 Stop all network management services.

Double-click the NMS Control shortcut at the desktop and enter the user name and

password to log in to the NMS Control.

Choose System > Stop All Services from the system menu.

Click Yes.

Step 3 Stop the operation system service of the NMS Server.

Choose Start > Control Panel > Administrative Tools > Services.

Right-click the NMSServer record and then choose Stop from the right-click menu.

Step 4 Modify the OuterIP parameter of the System.properties configuration file at the NMS Server and NMS Client 1.

Raisecom



12

Open the System.properties configuration file through the text document. By default, it is

saved at C:\NMS\PLATFORM\NNM5\globalconfig\System.properties.

Set the OuterIP parameter to the one of the public NIC A. If the public IP address of the

NMS Server is set to 10.0.0.1, set the OuterIP parameter is set to 10.0.0.1, as shown in

Figure 1-9.


Figure 1-9 Modifying the System.properties configuration file (2)

Step 5 Modify the ServiceComponent parameter of the NMS_Service.xml configuration file at the

NMS Server.

Open the NMS_Services.xml configuration file through the text document. By default, it

is saved at C:\ NMS\PLATFORM\NNM5\server\config\NMS_Services.xml.

Modify the ServiceComponent parameter and add the OuterIP parameter. For example, if

the public IP address of the NMS Server is changed to 10.0.0.1, the added OuterIP

parameter is set to 10.0.0.1, as shown in Figure 1-10.


Figure 1-10 Modifying the NMS_Services.xml configuration file (2)

Step 6 Start the NView NNM system.

Step 7 Start NMS Client 2 and add the IP address of the NMS Server.

Double-click the Client shortcut at the desktop.

Click .

Enter the name and IP address of the NMS Server and then click OK.

Step 8 Select the added NMS Server record and then click OK.

1.3 Operating environment requirements

1.3.1 Hardware environment requirements

When you deploy the NView NNM system, the recommended hardware configurations of the

PC are related to the networking application and network size. The followings describe

hardware environment requirements based on the networking application and network size.

Besides hardware requirements of the NMS Server, we recommend providing Uninterrupted

Power Supply (USP) for the NMS Server. This can prevent damaging the network

management database when the PC is powered off accidently.

Raisecom



13

In the following cases, the NMS Server hardware configurations are not deployed with performance collection. Performance metrics and parameters of the network are different. Therefore, requirements on PCs are different. You need to evaluate the hardware configurations based on the real application. Before deploying the NView NNM system, contact Raisecom technical support engineers. At least 5 GB idle disk space is required for upgrading the NView NNM system. If the disk space is not enough, a prompt will be displayed and the upgrade operation will fail.

MSAP networking mode

The followings show how to calculate the network size based on the chassis. Table 1-1 lists

hardware configurations of the PC.

One MSAP chassis = 1 RC006-12 chassis = 1 RC002-16 chassis

When the RC002 is cascaded, 1 RC002 = 1 MSAP chassis

Assume that 1 MSAP chassis is downlink connected to 30 remote devices.

Table 1-1 Hardware configurations of the PC (1)

Network size Recommended model of PC CPU main frequency RAM Disk space

0–500 chassis DELL PE T110 II Dual-core 2.7 GHz 2 GB Over 20 GB

Over 500 chassis DELL PE R310 Quad-core 2.53 GHz 4 GB Over 60 GB

EPON networking mode

The followings show how to calculate the network size based on the equivalent NE. Table 1-2

lists hardware configurations of the PC.

One OLT chassis = 20 equivalent NEs

One EOC = 5 equivalent NEs

One ONU = 1 CNU = 1 equivalent NE



0–10000 equivalent

NEs

DELL PE T110 II Dual-core 2.7 GHz 2 GB Over 20 GB

Over 10000 equivalent

NEs

DELL PE R310 Quad-core 2.53 GHz 4 GB Over 60 GB

Raisecom



14

MSAP+EPON hybrid networking mode

The followings show how to calculate the network size based on the equivalent NE. Table 1-3

lists hardware configurations of the PC.

One MSAP chassis = 1 RC006-12 chassis = 1 RC002-16 chassis = 30 equivalent NEs

One remote device = 1 equivalent NE

One OLT chassis = 20 equivalent NEs

One EOC = 5 equivalent NEs

One ONU = 1 CNU = 1 equivalent NE



0–10000

equivalent NEs

DELL PE T310 Dual-core 3.2 GHz Over 4 GB Over 20 GB

Over 10000

equivalent NEs

DELL PE R310 Quad-core 2.66 GHz Over 4 GB Over 60 GB

1.3.2 Operation system requirements

In Windows Server family operation systems, install, upgrade, and start the NView NNM system by using the administrator account. If you install, upgrade, and start the NView NNM system by using a non-administrator account, right-click the program or shortcut to be performed and then choose "Run as Administrator" from the right-click menu. Otherwise, configuration fails or the NMS Server is started improperly.

Supported operation systems

Table 1-4 lists operation systems supported by the NView NNM system. For a PC where the

NView NNM system is installed, its architecture and operation system should be matched.

The 32-/64-bit architecture should be installed with 32-/b4-bit operation system. Otherwise,

installation fails.

Table 1-4 Supported operation systems

Classification 32-bit operation system 64-bit operation system

NMS Server Windows Server 2003 SP2 Standard

X86 Windows Server 2003 SP2 Enterprise

X86 Windows XP SP3 Professional X86

Windows Server 2003 SP2 Standard X64 Windows Server 2003 SP2 Enterprise X64 Windows Server 2008 R2 Standard X64 Windows Server 2008 R2 Enterprise X64

NView NNM

PM service

Windows XP SP2 Professional X86 Windows XP SP3 Professional X86

Windows XP SP2 Professional X64 Windows 7 SP1 Professional X64

Raisecom



15

Classification 32-bit operation system 64-bit operation system

NMS Client Windows 7 SP1 Professional X86 Windows 7 SP1 Enterprise X86 Windows 7 SP1 Ultimate X86 Windows Server 2003 SP2 Standard

X86 Windows Server 2003 SP2 Enterprise

X86

Windows 7 SP1 Enterprise X64 Windows 7 SP1 Ultimate X64 Windows Server 2003 SP2 Standard X86 Windows Server 2003 SP2 Enterprise X86 Windows Server 2008 R2 Standard X64 Windows Server 2008 R2 Enterprise X64

We recommend that the NMS Server uses the Standard/Enterprise operation system. We recommend that the distributed NMS Clients uses the Professional/Ultimate operation system. Only English operation system is supported. Do not install the NView NNM system on the operation system with other languages. Otherwise, it may cause the following problems: The shortcut cannot be removed. Letters on NMS Client GUI may be digital gibberish. Information displayed on NMS Client GUI is incorrect. Other unknown problems about follow-up upgrade may occur.

Requirements on user privileges of operation system

When the NView NNM system runs on the Windows Server family operation system, you

should bring some requirements on user privileges of the operation system.

Table 1-5 lists requirements on user privileges of the operation system for installing,

upgrading, and starting the NView NNM system.

Table 1-5 Requirements on user privileges of operation system

Classification Privilege requirement

Install/upgrade/start the

NView NNM system

locally

Users, who log in to the operation system, must have the

administrator privilege.

We recommend using the administrator account to

install/upgrade/start the NView NNM system locally.

Install/upgrade/start the

NView NNM system

remotely

Users, who log in to the operation system, must belong to

the Administrators group and Remote Desktop Users group

simultaneously.

If the user does not belong to either of the 2 groups,

operation may fail.

In performance-distributed deployment mode, user privileges of PM service operation system must be identical to the ones of NMS Server operation system.

Raisecom



16

1.3.3 Interface requirements

When deploying the NView NNM system, you should consider requirements on interfaces.

Table 1-6 lists interface requirements. When the NView NNM system is running, ensure that

these interfaces are available for proper communication. They cannot be blocked/occupied by

the firewall or other software.

Interfaces, whose IDs are in boldface in Table 1-6, are basic interfaces for the NView NNM system. You must enable them.

Table 1-6 Interface requirements

Scenario Classification/Quantity Interface ID Remark

Normal use Database/3 13306: NView NNM

database 13303: iTN zero-

configuration database 3306: CEView database

Interface 13306 (NView

NNM database) must be

enabled. Interface 13303 must be

enabled if you use iTN remote

zero-configuration. Interface 3306 must be

enabled if you use the

CEView.

Message bus/2 61616: inter-process service

interface 61617: intra-process service

interface

They are must be enabled.

InstanceServer service/2 9302: event channel 9304: command channel


RMI/3 9362: intranet interface of

the resource model 9367: extranet interface of

the resource model 9364: management interface

of the resource model


Data center/3 9320: DCServer command

channel interface 9322: DCEMS command

channel interface 9323: DCEMS event channel

interface

You do not need to enable them

unless you wish to use the data

center.

Upgrade tool/5 9312: upgrade service

command channel 9314: upgrade service event

channel 9303: upgrade tool command

interface 9304: upgrade tool event

interface 9307: downloading the

upgrade packet through

HTTP


Raisecom



17


Channel traversal/103 16261: MSG NAT traversal 16262: iTN remote NAT

traversal 18080: Relay service

interface of WEB traversal 18081–18180: Web Agent

service interface pool of

WEB traversal

You do not need to enable

them. Transport devices: you must

enable interface 16262 when

you use iTN remote NAT

traversal. Other interfaces must be

enabled if you use enterprise

gateways.

Standard protocol stack/7 514: syslog 161and 162: SNNP 23: Telnet 22: SSH 21: FTP 69: TFTP 67: DHCP

You must enable these

interfaces. You can enable

them based on functions to be

used, You must enable interface 67

if you wish to use the

CEView.

JMX debugging interface

/4

9400: InstanceServer 9401: Client 9408: DCEMS 9409: DCServer

At present, only interface 9400

(InstanceServer) must be

enabled. You can enable other

interfaces if required.

Northbound

interface

CORBA/3 9317: northbound interface

service process 9315: naming service

process 9316: notification service

process

You do not need to enable the m

unless you wish to use the

CORBA northbound interface

of a transport device.

TL1/2 9381: RAW 9382: Telnet

You do not need to enable the m

unless you wish to use the TL1

northbound interface of an

EPON device.

WebService – You do not need to enable the

interface. You need to contact

Raisecom technical engineers to

specify an interface if you wish

to use WebService.

Alarm forwarding/2 9336: Socket forwarding 162: Trap PDU forwarding

You do not need to enable them.

Enable the related interface if

you wish to use Socket

forwarding or Trap PDU

forwarding.

Debugging

tool

JConsole 1099: debugging interface You do not need to enable the

interface unless you wish to

debug the system.

Raisecom



18


Dual-server

Warm-

standby

Dual-server Warm-

standby program/7

29001: server internal

communication 29002: data transmission 29003: alarm

synchronization/HTTP

communication 29004: disk Agent

communication 29005: mirroring driver

communication 29006: heartbeat detection 29007: client service

communication

You do not need to enable them

unless you wish to use dual-

server Warm-standby.

If dual-server warm-standby and Webservice are provided, you need to confirm interfaces to be occupied based on specific configurations, because these functions must be configured with specific interfaces. Interfaces, occupied by the dual-server warm-standby program in Table 1-6, are the ones used when you use default configurations for deployment.

1.3.4 Bandwidth requirements

To ensure the NMS Server and NMS Client or the master and slave servers in performance-

distributed deployment mode communicate with each other properly, at least 2 Mbit/s

bandwidth is required. If the bandwidth is over small, it may cause improper communication

and to fail providing network management functions, such as:

The NMS Client is started slowly.

Operations on the GUI of the NView NNM system are unsmooth.

1.3.5 Other requirements

Before installing the NView NNM system, confirm the following things:

In deployment mode, ensure that the PC is not installed with network management

software from other vendors. If there is any one, remove it and then install the NView

NNM system.

For the PC where the NMS Server program is to be installed, ensure that the SNMP Trap

Receiving Service of the Windows operation system is stopped.

Before installing/upgrading the NView NNM system, ensure all anti-virus software,

safety guard, and Trojan firewall are closed. Because when the NView NNM system is

being installed, it will register the system service. Operation will fail if you do not exit

these safety guard software.

Raisecom



19

1.4 Confirming installation procedures Before installing the NView NNM system, you need to confirm the installation procedures

and prepare related programs and License file.

Confirming installation procedures

To install the NView NNM system, follow these steps:

Step 1 Install the NView NNM system (kernel version V5.4.1) at the PC where the NMS Server is

installed.

Step 2 Upgrade the EMS through the upgrade packet.

Step 3 In performance-distributed deployment mode, install the PM service at the PM server. The

PM service is automatically upgraded after the NMS Server is upgraded successfully. Or,

upgrade the EMS through the upgrade packet.

Step 4 To management devices through multiple NMS Clients, install the NMS Clients at the NMS

Client PCs. The NMS Clients are automatically upgraded after the NMS Server is upgraded

successfully. Or, upgrade the EMS through the upgrade packet.

Preparing programs and License file

Before installing the NView NNM system, you need to prepare required programs and

License file, as listed in Table 1-7. Before installing the NView NNM system, you need to

save the installation program, upgrade package, and License file to the local hard-disk of the

PC.

Table 1-7 Preparing files

Program License file

NView NNM installation program

(kernel version V5.4.1) EMS upgrade package matching of

the device

License file matching with versions of the

NView NNM system (kernel version V5.4.1)

and EMS

The NView NNM system (kernel version V5.4.1) provides specified NMS Client installation program, which is of small size and is suitable for installing the NMS Client independently.

Raisecom

NView NNM (V5) Installation Guide 2 Installation steps


20

2 Installation steps

This chapter describes how to install the NView NNM system, including the following

sections:

Installing NView NNM system

Installing NMS Client

Installing distributed PM service

Upgrading NView NNM system

2.1 Installing NView NNM system In centralized deployment mode, install the NMS Server, NMS Client, and PM service

by following these steps.

In performance-distributed deployment mode, install the NMS Server by following these

steps and the install the distributed PM service program. For details about how to install

the distributed PM service see section 2.3 Installing distributed PM service.

For a PC where the NView NNM system is installed and then is removed, you

need to remove the original installation file before re-installing the NView NNM system. The original network management data will be removed and cannot be restored after you delete the installation file. Therefore, copy the whole installation file and keep it well before removing it. Perform this operation with care.

During installation, the system will check the installation path. If there is any non-deleted file, a prompt appears and the system exits installation progress. Before re-install the NView NNM system, delete the original installation file.

Step 1 Double-click the NView NNM installation program and a dialog box appears, where you

should select a language.

Step 2 Click Next and a dialog box appears, as shown in Figure 2-1. The licence agreement

describes the usage agreement in details. Read this agreement carefully before installing the

NView NNM system. If you accept the above agreement, select the I accept the terms of the

license agreement radio box. Otherwise, click Cancel.

Raisecom



21

Figure 2-1 License agreement

Step 3 Click Next and a dialog box appears, as shown in Figure 2-2. Install different components

based on the role of the PC, as listed in Table 2-1.

Table 2-1 Functions of PCs and installation components

Role of PC Function Description

Server Be installed with the

NMS Server.

Install the NMS Server, NMS Client, and

NMS Control if you select this radio box.

By default, this radio box is selected.

Client Be installed with the

NMS Client.

Install the NMS Client if you select this

radio box.

Distributed PM

service

Be installed with the

NMS Control.

Install the NMS Control if you select this

radio box.

Raisecom



22

Figure 2-2 Selecting components to be installed

Step 4 (Optional) select the installation path of the NView NNM system. By default, it is

C:\NMS\PLATFORM\. To select another one, click Browse.

To install the NView NNM system at another installation directory, no space should be contained in the path name. Otherwise, the NView NNM system fails to be started.

Step 5 Click Next and a dialog box appears, as shown in Figure 2-3. To install the NView NNM

system, the matching License file is required. Click Browse and then select the License file.

Raisecom



23

Figure 2-3 Selecting the License file

Step 6 Click Next and a dialog box appears, as shown in Figure 2-4.

Choose the IP address of the NMS Server from the Server IP Address drop-down list.

In NAT or dual-NIC networking environment, if the NMS Server is in the private

network and the NMS Client is in the public network, you need to configure the NAT-

translated IP address or the one of the public NIC. When you install distributed NMS

Clients, you need to enter the IP address of the public network. When NMS Clients,

which are in the public network, access the NMS Server, they need the NAT-translated IP

address or the one of the public NIC.

In performance-distributed deployment mode, the PM Server and NMS Server need to be deployed at the same network. The PM Server needs to communicate with the NMS Server and managed devices.

Raisecom



24

Figure 2-4 Selecting the IP address of the NMS Server

Step 7 Click Next and a dialog box appears, as shown in Figure 2-5. At this dialog box. MySQL

database is to be installed by default. In general, no modification is made.

Figure 2-5 Installation mode of MySQL database

Raisecom



25


Figure 2-6 Confirming installation information


Raisecom



26

Figure 2-7 Installation file

Step 10 Click Install. After configurations, a dialog box appears, as shown in Figure 2-8.

Figure 2-8 Installing the NView NNM system completely

Raisecom



27

Step 11 Click Finish.

Up to now, the NView NNM system is installed completely and the following shortcuts

appear on the desktop.

: be used to start the NMS Server.

: be used to start the NMS Control.

: be used to start Client.

: be used to start the upgrade tool.

: be used to start the network management and maintenance tool.

In addition, the start shortcut of the NView NNM system will be automatically added to the

Start menu of the Windows operation system, as shown in Figure 2-9.

Figure 2-9 Start menu (1)

2.2 Installing NMS Client

Only when you need to use other PCs to manage devices, you can install NMS Clients on them. The NMS Client can be installed in 2 modes. In these 2 modes, the operation steps and interfaces are identical while installation programs are different.

Installing the NMS Client through the independent NMS Client installation program:

distributed NMS Clients are installed through the independent NMS Client installation program.

Raisecom



28

Installing the NMS Client through the NView NNM installation program: the NView

NNM installation program is a complete set, which supports installing the NMS Client

only.

Installing NMS Client through independent NMS Client installation program

Step 1 Double-click the NView NNM installation program.

Step 2 Select a language and then click Next.

Step 3 If you accept the license agreement, select the I accept the terms of the license agreement

radio box. Otherwise, click Cancel.

Step 4 Click Next and then select the installation path of the NMS Client. By default, it is

C:\NMS\PLATFORM\.

Step 5 (Optional) to select another installation path, click Browse.

To install the NMS Client at another installation directory, no space should be contained in the path name. Otherwise, the NMS Client fails to be started.

Step 6 Click Next and then enter the IP address of the NMS Server.

Enter the IP address of the NMS Server at Server IP Address text box.







Step 7 Click Next and then confirm the installation information.

Step 8 Click Next.

Step 9 Click Install.


Up to now, the NMS Client is installed completely and the following shortcuts appear on the

desktop.



In addition, the start shortcut of the NMS Client will be automatically added to the Start menu

of the Windows operation system, as shown in Figure 2-10.

Raisecom



29


Installing NMS Client through NView NNM installation program





Step 4 Click Next and then select the Install NMS Client radio box only.


C:\NMS\PLATFORM\.


To install the NMS Client at another installation directory, no space should be contained in the path name. Otherwise, the NMS Client fails to be started.


Enter the IP address of the NMS Server at Server IP Address text box.








Step 9 Click Next.



Up to now, the NMS Client is installed completely and the following shortcuts appear on the

desktop.



Raisecom



30

In addition, the start shortcut of the NMS Client will be automatically added to the Start menu

of the Windows operation system, as shown in Figure 2-11.


2.3 Installing distributed PM service

Only in performance-distributed deployment mode, you can install the PM service automatically.





Step 4 Click Next and then select the Install PM Service radio box only.


C:\NMS\PLATFORM\.


To install the NMS Control at another installation directory, no space should be contained the path name. Otherwise, the PM service fails to be started.



Step 9 Click Next.



Up to now, the PM service program is installed completely and the following shortcuts appear

on the desktop.

: be used to start the NMS Server.

Raisecom



31

: be used to start the NMS Control.


In addition, the start shortcut of the NMS Control will be automatically added to the Start

menu of the Windows operation system, as shown in Figure 2-12.


2.4 Upgrading NView NNM system

After installing the NView NNM system, upgrade it by using the upgrade tool and matching packet. Distributed PM Servers or independently-installed NMS Clients can be upgraded manually or automatically. This section describes how to upgrade the NMS Server only. In centralized

deployment mode, upgrade the NMS Server, NMS Client, and PM service by following these steps. To upgrade distributed NMS Clients and PM Servers manually, follow these steps.

For details about how to upgrade distributed NMS Clients and PM Servers automatically and the upgrade tool, see NView NNM (V5) Upgrade Guide.

After installing the NView NNM system, upgrade it by using the upgrade tool and matching packet directly. Do not start the NView NNM system before or during upgrade.

Step 1 Double-click the Upgrade shortcut to start the upgrade tool.

Step 2 Click Please specify the upgrade packet. A dialog box appears. Select the local upgrade

packet.

Step 3 Click Please specify the backup directory. A dialog box appears. Select the backup

directory.

Step 4 Click Upgrade. The process information is displayed at the dialog box. Figure 2-13 shows

the prompt contents after upgrade.

Raisecom



32

Figure 2-13 Upgrading the NView NNM system successfully

Raisecom

NView NNM (V5) Installation Guide 3 Starting configurations


33

3 Starting configurations

This chapter describes how to configure the NView NNM system to be started automatically

with the operation system and how to start services of the NView NNM system, including the

following sections:

Configuring NView NNM to be started automatically with operation system

Configuring services to be started automatically with NView NNM system

3.1 Configuring NView NNM to be started automatically with operation system

After you configure the NView NNM system to be started automatically after the PC is

powered on, the NView NNM system is started automatically once the PC is powered on and

the operation system is started successfully. In addition, you can configure services of the

NView NNM system to be started automatically through the NMS Control. Therefore, the

NView NNM is available once the PC is powered on.

To configure the NView NNM system to be started automatically with the operation system,

follow these steps:

Step 1 Choose Start > Control Panel > Administrative Tools > Services, right-click the

NMSServer record, and then choose Properties from the right-click menu.

Step 2 Choose Automatic from the drop-down list.

Step 3 Click OK.

3.2 Configuring services to be started automatically with NView NNM system

After you configure network management services to be started automatically with the NView

NNM system, these services will be automatically started after the NView NNM system is

started. In addition, orders for starting these services are correct.

To configure services to be started automatically with the NView NNM system, follow these steps:

Raisecom

NView NNM (V5) Installation Guide 3 Starting configurations


34

Step 1 Double-click the NMS Server shortcut. A dialog box appears, saying "NMS Server has been

started successfully!" Click OK.

In Windows Server family operation systems, no dialog box will appears after the NMS Server is started.

Step 2 Double-click the NMS Control. Enter the user name and password and then click OK to log

in to the NMS Control. The user must be the administrator or the one in the administrator

group of the NView NNM system. By default, the user name is administrator and the

password is raisecom.

Step 3 Right-click a record at the Services tab and then choose Startup Type > Automatic from the

right-click menu.

By default, the startup mode of the InstanceServer service is set to automatically. It means that the InstanceServer service is automatically started after the NView NNM system is started. The InstalceServer service is the most important one of the NView NNM system. It must be started when you use the NView NNM system.

Step 4 (Optional) right-click the stopped PM service and then choose Start from the right-click

menu to start the PM service manually.

Step 5 (Optional) right-click the running PM service and then choose Stop from the right-click menu

to stop the PM service manually.

Raisecom

NView NNM (V5) Installation Guide 4 Modifying and removing NView NNM system


35

4 Modifying and removing NView NNM system

This chapter describes how to modify and remove the NView NNM system, including the

following sections:

Modifying NView NNM installation program

Removing NView NNM system

4.1 Modifying NView NNM installation program Modifying the NView NNM installation program refers to installing the NView NNM

component programs on the PC. This operation is unavailable in centralized deployment

mode. In general, this operation is suitable for adding component programs to distributed

NMS Client or PM server. Component programs and scenarios, which support modifying the

NView NNM installation program, are shown as below.

PM service: on distributed NMS Client PCs, by adding the PM service program, you can

install the PM service.

NMS Client: on distributed PM servers, by adding the NMS Client program, you can

deploy distributed NMS Clients.

For installed programs, you cannot remove or re-install them by modifying the

NView NNM installation program. The removal operation refers to removing the NView NNM system instead of one

or multiple independent programs.

Step 1 Double-click the NView NNM installation program and a dialog box appears, as shown in

Figure 4-1.

Step 2 Select the Modify radio box and then click Next.

Step 3 Select programs to be added and then click Next.

Step 4 Install the selected programs. Operation interfaces and steps are identical to the ones for

executing them. For details, see chapter 2 Installation steps.

Raisecom



36

Figure 4-1 Modifying the NView NNM installation program

4.2 Removing NView NNM system You can remove the NView NNM system when it is not required.

To remove the NView NNM system, stop it (including the NMS Server and NMS Client) in

advance. When you remove the NView NNM system, the system will automatically check

whether the NMS Server is stopped and will display a dialog box if it is not stopped. To

remove the NView NNM system, follow these steps:

We recommend backing up configurations of the NView NNM system manually before removing it. If you need the data of the NView NNM system, data center file, or need to recover the NView NNM system, you can use the backups. To back up configurations of the NView NNM system manually, stop all programs of the NView NNM system and copy the whole installation file.

Step 1 To remove the NView NNM system through the Windows operation system, choose Start >

All Programs > NMS > UnInstall NMS, as shown in Figure 4-2.

Raisecom



37

Figure 4-2 Menus for removing the NView NNM system

Step 2 (Optional) to remove the NView NNM system through the Control Panel of the Windows

operation system, choose Start > Control Panel > Add or Remove Programs, select the

NMS record, and then click Remove, as shown in Figure 4-3.

Figure 4-3 Removing the NView NNM system through the Control Panel

Step 3 A dialog box appears, as shown in Figure 4-4.

Raisecom



38

Figure 4-4 Removing the NView NNM system


Figure 4-5 Confirming the removal operation

Raisecom



39

Step 5 Click Yes. The system begins to remove the NView NNM system.

Step 6 After removal, the system prompts you to restart the PC, as shown in Figure 4-6.

Figure 4-6 Prompting to restart the PC

Step 7 Click Finish and the PC will be restarted.

Step 8 After removing the NView NNM system, confirm the contents of the NView NNM

installation directory. Data and logs of users are saved at the directory. Therefore, keep it

properly.

Raisecom

NView NNM (V5) Installation Guide 5 FAQ


40

5 FAQ

This chapter describes some questions encountered during installing and removing the NView

NNM system.

5.1 How to stop SNMP Trap service of Windows operation system?

On a PC, where the NView NNM system is installed, the SNMP Trap Service of the Windows

operation system should be stopped. To stop the SNMP Trap Service of the Windows

operation system, follow these steps:

Step 1 Choose Start > Control Panel > Administrative Tools > Services.

Step 2 Right-click the SNMP Trap Service and then choose Properties from the right-click menu.

Step 3 Choose Manual from the Startup type drop-down list and then click Stop.

5.2 Why does NView NNM system fail to receive alarms sent by NEs?

To ensure that an alarm can be received and displayed properly by the NView NNM system,

ensure to meet the following requirements:

All managed devices and the management station, where the NView NNM system is,

should be connected to the network properly. In addition, links among them should be

reachable. They can be ping through and communicate through the User Data Protocol

(UDP).

Interface 162 of the PC, where the NMS Server is installed cannot be occupied. For

example, in Win2000 Server operation system, the SNMP Trap Service is started by

default. This service occupied interface 162. Before installing the NView NNM system

on this operation system, stop the SNMP Trap Service. Otherwise, the NView NNM

system fails to receive alarms.

Raisecom



41

This requirement is designed for the PC where the NMS Server in installed. It is not required for PCs where the NMS Clients are installed.

In general, interfaces for the NView NNM system include interfaces 9303–9336 and

interface 13306. Ensure that these interfaces are not intercepted by the firewall or

occupied by other programs.

The network must allow transmitting data through UDP. In some specific environment,

all devices are hidden behind a firewall for network security. In this case, you must

ensure that the Trap can pass through the firewall and then reach the management station

after. Otherwise, the NView NNM system fails to receive alarms.

Agent of managed device must properly set the Trap target address to the IP address of

the PC where the NMS Server is. In NAT network, the Trap target address is the IP

address of the NView NNM system before translation. In dual-NIC network, the Trap

target address is the IP address of the private network where the NView NNM system is.

In the NView NNM system, the alarm must be defined in details. Otherwise, the alarm is

regarded as an unknown one even the NView NNM system receives it.

Ensure that there is no filtering condition set for the alarm in the NView NNM system.

Otherwise, the alarm cannot be displayed or processed.

The device, where the alarm is generated, must register a related node in the NView

NNM system (the node must in the device list). Otherwise, the NView NNM system will

discard the unknown alarm.

The node of the device, where the alarm is generated, must be a one in the management

domain of the administrator. Otherwise, the alarm is not displayed. The alarm can be

received by the NView NNM system but not displayed at the NMS Client to which the

administrator logs. If the administrator logs in to the NMS Client as the member of the

admin group, no restriction is available.

The EMS version and the Agent program version of the device must be matched.

Otherwise, the NView NNM system fails to receive some alarm.

If the above requirements are met, the NView NNM system can receive and analyze alarms

properly. The above requirements are the least ones for the NView NNM system receiving

alarms. In some cases, other requirements should be met.

5.3 Why do distributed NMS Clients fail to connect to NMS Server?

Check whether the NMS Server is started and runs properly.

Check whether you properly enter the IP address of the PC, where the NMS Server is

installed, when you install the NMS Client. If the NMS Client fails to connect to the

specified NMS Server, the system will prompt you to re-enter the IP address of the PC,

where the NMS Server is installed.

Check whether the ACL feature of NView NNM users is enabled. If it is enabled, on the

local NMS Client, register the IP address of the PC, where the remote NMS Client is.

Otherwise, the remote NMS Client fails to connect to the NMS Server.

Raisecom



42

5.4 Why does NMS Server fail to connect to database when being started?

Check whether the database service is started properly. Choose Start > Control Panel >

Administrative Tools > Services to check whether the Nms_database_engine service is

started. If it is not started, right-click the Nms_database_engine service and then choose

Start from the right-click menu to manually start the service.

Close the firewall or configure the firewall to allow accessing the database.

Check whether the NView NNM system is attacked by the MySQL worm virus when the

NView NNM system uses the MySQL database. Use the anti-virus software to clear the

virus.

5.5 Why does system prompt communication timeout or SNMP operation failure when EMS is being started?

Check whether the master network management module works properly.

Check whether the system LED and Ethernet interface LED are working properly.

Check whether the network management card is inserted properly.

Check whether the route is reachable by ping the IP address of the node.

Check whether the SNMP packet can be transmitted properly by performing SNMP Ping

operation on the IP address of the node through the SNMP Ping tool of the NView NNM

system or the MIB tool.

Check whether the version of the EMS is matched with that of the master network

management module.

Check whether the device type in the topology view is consistent with the real one.

Check whether the SNMP information (communities) registered by the node is

consistent with the one configured on the master network management module. By

default, the name of the read-only community is set to public and the name of the read-

write community is set to private.

Adjust the SNMP timeout and retry parameters based on the network condition.

5.6 How to eliminate scrambled characters when the NView NNM system is installed for a non-Einglish system?

Step 1 Choose Start > Control Panel > Regional and Language Options and a dialog box appears,

Step 2 Choose English (Unite States) from the drop-list menu at the Regional Options tab, as shown

below.

Raisecom



43

Step 3 Choose English (Unite States) from the drop-list menu at the Advanced tab, as shown below.

Raisecom



44

5.7 Why does the InstanceServer service fail to be started with an "Unable to load JMV" prompt box being displayed?

When being started, the virtual server needs to load the MSVCR71.DLL file. However, some

operation systems do not provide this file. Therefore, prompt boxes will appear, as shown

below:

Figure 5-1 Prompt box (1)

Raisecom



45

Figure 5-2 Prompt box (2)

The following figure shows where the MSVCR71.DLL file is located.

You need to copy the MSVCR71.DLL file to the location, as listed in the following figure.

Raisecom



46

This problem will not happen to supported operation systems listed in this guide. It happens when you install the NView NNM system for an untested operation system. When the problem is resolved, we cannot ensure that the NView NNM system will work properly. Therefore, we recommend installing operation systems supported by the NView NNM system.

Raisecom

NView NNM (V5) Installation Guide 6 Appendix


47

6 Appendix

This chapter describes terms and abbreviations involved in this guide, including the following

sections:

Terms

Abbreviations

6.1 Terms

A

Alarm Traps that are sent when the device or the NView NNM system detects a

fault.

C

Customer

The customer uses services provided by the device. The customer

information can be attached with the NE or alarm. The customer

information is saved in the NView NNM system only.

D

Data center

In the NView NNM system, the data center is an auxiliary program. It

backs up and upgrades the system software and configuration files of the

devices and maintains their versions.

Data dump

Data records in the NView NNM database are exported from the database

and saved to files. The NView NNM system supports data dump on logs,

historical alarms, performance collection data, and system monitoring

collection data.

Device scan It can be used to scan devices in the IP address range and add them to the

NView NNM system.

Domain The domain takes the NE as the minimum granularity. It refers to

collection of resources that can be operated by users.

E

Raisecom



48

Equivalent NE

Each NE can be converted in to the equivalent NE based on its equivalent

coefficient. It facilitates calculating the management capability of the

NView NNM system.

H

History alarm It refers to all cleared/filtered alarms.

I

Inventory Resources in the NView NNM system

L

License It refers to the authorization file of the NView NNM system. The License

file defines network management functions available for users.

N

Network

element The device is managed as the NE in the NView NNM system.

NMS Monitor

Auxiliary program of the NView NNM system. It can manage all service

programs of the NView NNM system and monitor the operating status of

the NView NNM system.

Node Name for subnets, NEs, or symbols in the NView NNM system.

Northbound

interface

It is an interface program between the NView NNM system and the upper

network management system. The upper network management system

can manage devices through the northbound interface.

O

Operate

privilege

Authority used to operate and manage the NView NNM system and its

resources

P

Performance

monitor

The NView NNM system collects and displays the traffic or packet loss

rate of devices.

Polling It can be used to periodically detect whether the device is offline.

S

Symbol The symbol is a schematic node, which cannot be managed. However, it

can display the network topology better.

Raisecom



49

Synchronization

With synchronization, the NView NNM system can update device

resources or alarm information in the database. Therefore, the NView

NNM system and the device can keep consistent.

Syslog Device logs that meet the Syslog protocol format defined in RFC3164

T

Topology

Graphical network topology in the NView NNM system. It displays the

networking application, alarms generated on subnets or NEs, and status

of nodes.

Trap The mode for a device sending alarms to the NView NNM system. It is

sent to the NView NNM system through the SNMP packet.

U

User

The NMS Client user and the domain and operation privilege of the user

and its user group define the network management functions available for

the user.

User Group The user group can provide identical domain and operation privilege for

users in the group.

6.2 Abbreviations

C

CORBA Common Object Request Broker Architecture

CPU Central Processing Unit

E

EPON Ethernet Passive Optical Network

F

FTP File Transfer Protocol

I

IP Internet Protocol

N

NMS Network Management System

Raisecom



50

NNM Network Node Management

O

ONU Optical Network Unit

S

SNMP Simple Network Management Protocol

U

UDP User Datagram Protocol

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: [email protected]

Date post:	29-Apr-2018
Category:	Documents
Upload:	dinhminh
View:	269 times
Download:	9 times

NView NNM (V5) Installation Guide (Rel 43) - DAVANTEL NNM (V5) Installation Guide (Rel_43).pdf ·...

Documents