NView NNM (V5) Installation Guide (Rel - 46)

www.raisecom.
com
NView NNM (V5)

Installation Guide
(Rel_46)
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: Raisecom Building, No. 11, East Area, No. 10 Block, East Xibeiwang Road, Haidian District, Beijing,
P.R.China.
Postal code: 100085
-----------------------------------------------------------------------------------------------------------------------------------------
Notice
Copyright 2015
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
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 Proprietary and Confidential

i
Copyright Raisecom Technology Co., Ltd.
Raisecom
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.

ii
Raisecom
Change history
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Issue 46 (2015-07-01)
Seventh commercial release
Added descriptions of installation and deployment of the green version NMS Client.
Updated interface requirements of the NView NNM system.
Issue 45 (2015-04-01)
Sixth commercial release
Updated recommended configurations of the host of NMS Server.
Updated interface requirements of the NView NNM system. Added data interface in the
distributed performance deployment mode.
Issue 44 (2014-06-01)
Fifth commercial release
Revised the installed program according installation FILE of NView NNM kernel V5.4.4.
Updated installation when using the respective installation FILE in performance
distributed deployment.
Updated descriptions of the distributed PM service updating automatically.
Updated interface requirements of the NView NNM system.
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 descriptions of deploying the NMS Client.
Updated descriptions of the installation procedure of NView NNM kernel V5.4.1 based
on the installation FILE of NView NNM kernel V5.4.1.
Updated interface requirements of NView NNM system.
Issue 42 (2013-06-01)
Third commercial release
Added descriptions of the installation procedure of performance-distributed deployment
based on the installation FILE of NView NNM kernel V5.4.1.
Updated descriptions of the installation procedure of NView NNM system kernel V5.4.1
based on the installation FILE of NView NNM kernel V5.4.1.

iii
Raisecom
Issue 41 (2012-09-01)
Second commercial release
Added descriptions of cases where the License is not compatible with the NView NNM
system version.
Updated descriptions of the installation procedure of NView NNM kernel V5.4.1. The
installation steps are identical to the ones of NView NNM system kernel V5.4.
Issue 40 (2012-06-01)
Initial commercial release

iv
Raisecom
NView NNM (V5) Installation Guide Contents
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 .................................................................................................................... 8
1.2.3 Deployment modes of NMS Client ......................................................................................................... 8
1.3 Operating environment requirements ............................................................................................................. 13
1.3.1 Hardware environment requirements .................................................................................................... 13
1.3.2 Operation system requirements ............................................................................................................. 15
1.3.3 Interface requirements ........................................................................................................................... 17
1.3.4 Bandwidth requirements ....................................................................................................................... 19
1.3.5 Other requirements ................................................................................................................................ 20
1.4 Confirming installation procedures ................................................................................................................ 20
2 Installation steps ......................................................................................................................... 22

2.1 Installing NView NNM system ...................................................................................................................... 22
2.2 Install green version NMS Client ................................................................................................................... 29
2.2.1 Make an archive .................................................................................................................................... 30
2.2.2 Installation............................................................................................................................................. 31
2.2.3 (Optional) create shortcut on the desktop ............................................................................................. 32
2.3 Installing NMS Client .................................................................................................................................... 32
2.4 Installing distributed PM service .................................................................................................................... 35
2.5 Upgrading NView NNM system .................................................................................................................... 36
3 Starting configurations .............................................................................................................. 38

3.1 Configuring NView NNM to be started automatically with OS ..................................................................... 38
3.2 Configuring services to be started automatically with NView NNM system ................................................. 38
4 Uninstalling NView NNM system .......................................................................................... 40

4.1 Uninstall NMS Server or Client ..................................................................................................................... 40
4.2 Uninstall PM service ...................................................................................................................................... 43
5 FAQ ................................................................................................................................................ 44
5.1 How to stop SNMP Trap service of Windows OS? ........................................................................................ 44

v
Raisecom
NView NNM (V5) Installation Guide Contents
5.2 Why does NView NNM system fail to receive alarms sent by NEs? ............................................................. 44
5.3 Why do distributed NMS Client fail to connect to NMS Server? .................................................................. 45
5.4 Why does NMS Server fail to connect to database when being started? ........................................................ 46
5.5 Why does system prompt communication timeout or SNMP operation failure when EMS is being started? 46
5.6 How to eliminate scrambled characters when the NView NNM system is installed for a non-Einglish system?
.............................................................................................................................................................................. 46
5.7 Why does the InstanceServer service fail to be started with an "Unable to load JMV" prompt box being
displayed?............................................................................................................................................................. 48
6 Appendix ...................................................................................................................................... 51
6.1 Terms .............................................................................................................................................................. 51
6.2 Abbreviations ................................................................................................................................................. 53

vi
Raisecom
NView NNM (V5) Installation Guide Figures
Figures
Figure 1-1 Centralized deployment ........................................................................................................................ 2

Figure 1-2 Performance distributed deployment .................................................................................................... 3
Figure 1-3 NMS Server and NMS Client at the same network .............................................................................. 9
Figure 1-4 NAT network environment ................................................................................................................... 9
Figure 1-5 Dual-NIC network environment ......................................................................................................... 10
Figure 1-6 Modifying the System.properties configuration file (1) ..................................................................... 10
Figure 1-7 Modifying the NMS_Services.xml configuration file (1) ................................................................... 11
Figure 1-8 Deploying NMS Client in dual-NIC environment .............................................................................. 12
Figure 1-9 Modifying the System.properties configuration file (2) ..................................................................... 12
Figure 1-10 Modifying the NMS_Services.xml configuration file (2) ................................................................. 13
Figure 2-1 License agreement .............................................................................................................................. 23
Figure 2-2 Selecting components to be installed .................................................................................................. 24
Figure 2-3 Selecting the License file .................................................................................................................... 25
Figure 2-4 Selecting the IP address of the NMS Server ....................................................................................... 26
Figure 2-5 Installation mode of MySQL database ............................................................................................... 26
Figure 2-6 Confirming installation information ................................................................................................... 27
Figure 2-7 Installation file .................................................................................................................................... 28
Figure 2-8 Installing the NView NNM system completely .................................................................................. 28
Figure 2-9 Start menu (1) ..................................................................................................................................... 29
Figure 2-10 Command line window ..................................................................................................................... 30
Figure 2-11 Example for archive file ................................................................................................................... 31

Figure 2-12 Shortcut icon of Client on the desk ................................................................................................... 32
Figure 2-13 Start menu (2) ................................................................................................................................... 33
Figure 2-14 Start menu (3) ................................................................................................................................... 34
Figure 2-15 Start menu on the PC with performance distributed deployment ..................................................... 36
Figure 2-16 Upgrading the NView NNM system successfully ............................................................................ 37

vii
Raisecom
NView NNM (V5) Installation Guide Figures
Figure 4-1 Menus for uninstalling the NView NNM system ............................................................................... 41
Figure 4-2 Removing the NView NNM system through the Control Panel ......................................................... 41
Figure 4-3 Removing the NView NNM system ................................................................................................... 42
Figure 4-4 Confirming the removal operation ...................................................................................................... 42
Figure 4-5 Prompting to restart the PC ................................................................................................................ 43

Figure 5-1 Prompt box (1) .................................................................................................................................... 48
Figure 5-2 Prompt box (2) .................................................................................................................................... 49

viii
Raisecom
NView NNM (V5) Installation Guide Tables
Tables
Table 1-1 Specific configuration parameters of the Dell Edge R320 server ........................................................ 13
Table 1-4 Supported OSs...................................................................................................................................... 16
Table 1-5 Requirements on user privileges of OS ................................................................................................ 17
Table 1-6 Interface requirements .......................................................................................................................... 17
Table 1-7 Preparing files ...................................................................................................................................... 21
Table 2-1 Functions of PCs and installation components ..................................................................................... 23

ix
Raisecom
NView NNM (V5) Installation Guide 1 Preparing for configurations
1 Preparing for configurations
The chapter describe features and preparations 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 V5.4.1 to kernel V5.4.4. The NView
NNM kernel V5.4.4 covers all features of the NView NNM kernel 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 to use.
The NView NNM system kernel V5.4.4 provides matching installation FILE and EMS
versions. After installing the NView NNM system kernel V5.4.4, you need to use the
matching EMS upgrade package 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 Proprietary and Confidential 1

Raisecom
Figure 1-1 Centralized deployment
Performance distributed deployment: the PM service of the NView NNM system can be
installed independently. This helps to reduce resource 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 share the hardware processing pressure of the NMS server and improve
the performance and efficiency of the NMS Server, expanding the PM ability.
Performance distributed deployment mode is not required if you do not need to

monitor the performance data. To monitor performance data in centralized
deployment mode, install the PM service on the NMS server.

Raisecom
Figure 1-2 Performance distributed deployment
Installation and deployment modes of NMS Client

In either of the 2 deployment modes, the NMS Client 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 kernel V5, you need to use the installation FILE of NView NNM
kernel V5.4.4 and the matching upgrade package. 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.
The installation FILE 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:

Raisecom
Installation FILE of the NView NNM system: include the NMS Server and NMS Client.
Be grouped into 32-bit and 64-bit installation FILEs: related to 32-bit and 64-bit
architecture and OSs.
The file name is set to NView_NNM_V5_timestamp_operation system type.
For example, for the file name NView_NNM_V5_20140603_win32.exe, the
NView_NNM_V5 indicates the NView NNM system; the 20140603 indicates that
the timestamp is set to June 3, 2014; the win32 indicates that the installation system
fits for 32-bit Windows OS.
PM service installation FILE of the NView NNM system: includes the PM service
program only.
The file name is NView_NNM_V5_timestamp_OS type.
For example, for the file name NView_NNM_V5_20140603_win32.exe, the
NView_NNM_V5 indicates the PM service; the 20140603 indicates that the
timestamp is set to June 3, 2014; the win32 indicates that the installation system fits
for 32-bit Windows OS.
Installation FILE of the NMS Client: include the NMS Client only.
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 OS.
The PM service installation FILE of the NView NNM system needs to be used with
installation FILE of the NView NNM kernel V5.4.4.
Installation features
The installation FILE of NView NNM kernel 5.4.5 supports the following features:
Support independent NMS Server installation FILE. You can install programs of the
NMS Server and integrated NMS Client or install the NMS Client independently.
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 installation FILE of the PM service, which is only suitable for
installing the PM service, and support installing the PM service on multiple PCs.
Support independent NMS Client installation FILE to install the NMS Client only.
Support installation FILEs for 32-bit and 64-bit NMS Server, PM service, and NMS
NMS Client. You can select the installation FILEs based on the PC architecture and OS.
After the PM service is installed and updated on the NMS server, NMS supports
generating the archive of the Green version NMS Client. Copy or download the archive,
and decompress it to the local disk. Then, distributed NMS Client is deployed.

Raisecom
During network management, it is crucial to provide continuous network management

services for network maintenance. In the traditional cases, if a network server crashes, it
will cause NMS to stop all services.
The NMS supports High Availability (HA) deployment mode.
You must select the installation FILE based on the architecture and OS of the PC.
The architecture and OS must be matched. The 32-/64-bit architecture should be
installed with 32-/b4-bit OS. 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.
The HA system is usually composed of two physical servers. One provides the
service as an active server. When it fails, the other server takes over network
management service from it to fulfil the HA requirement.
Install the NView NNM system on the server deployed the HA feature, when a fault
occurs, the system will minimize the downtime to promote availability. In the NEC
ExpressCluster integrated case, dual-server hot backup provides the HA feature to
the NView NNM system, for details see the related manual to the integrated case.
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 Client 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.

Raisecom
Process various operations logically.

Support hierarchical, privilege-based, and domain-based security management.
Support system monitoring.
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.
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 FILE
and upgrade package.
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 Client, you can realize hierarchical,
privilege-based, and domain-based configuration and management mode. In addition, you can
monitor multiple physical locations simultaneously.
Green version NMS Client program

The green version NMS Client can be used after recompression. It is easy and flexible to
deploy. Except creating a shortcut on the desktop manually, the green version NMS Client is
the same with common NMS Client.
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 V5.4.4 or later
replaces the earlier than kernel V5.4. Therefore, the original performance service and
performance probe programs are replaced by the PM service program.

Raisecom
In centralized deployment mode, the PM service with kernel version V5.4.4 will
replace the original performance program. After finishing the deployment on the
Server, need to independently install the PM service to finish the deployment.
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.
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.
The PM service in performance distributed deployment mode only supports updating
automatically.
Follow-up upgrade of NMS Client

After the NMS Server is upgraded successfully, there are three methods for upgrading
distributed NMS Client:
Support manually generating archive of the green version NMS Client on the Server.
After copying/downloading and decompressing the archive to the local disk, the
upgraded NMS Client can be used.
When the NMS Client is being started, it will connect to the upgraded NMS Server and
be upgraded automatically.

Raisecom
In addition, you can use the upgrade tool and upgrade package to manually upgrade the
NMS Client.
1.2.2 Selecting deployment mode

The deployment modes of the NView NNM kernel V5.4.4 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, and supports deploying multiple PM services. This deployment mode is
suitable for large network.
In the performance distributed deployment mode, PCs where the NMS Server and
the distributed PM service are installed need to be in the same network.
1.2.3 Deployment modes of NMS Client

The NMS Client 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.
Networking environment of distributed deployment

When deploying the NMS Client in distributed mode, note the network environment between
the NMS Client and NMS Server.
If the NMS Server and NMS Client are at the same network, they can access each other
and the NMS Server can manage the NMS Client, as show in Figure 1-3.
If the NMS Server and NMS Client 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 Client through the IP address of the extranet. The
NMS Client is connected to the IP address of the public NIC of the NMS Server.

Raisecom
Figure 1-3 NMS Server and NMS Client at the same network
Figure 1-4 NAT network environment

Raisecom
Figure 1-5 Dual-NIC network environment
Modifying configuration parameters of NAT/dual-NIC environment

When deploying the NMS Client 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.
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 OS 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)

Raisecom
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 Client in dual-NIC environment

As shown in Figure 1-8, NMS Client is 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.
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.

Raisecom
Figure 1-8 Deploying NMS Client 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 OS 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.
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.

Raisecom
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
The hardware configurations to the host on the NMS Server are shown in Table 1-1, Table 1-2,
and Table 1-3.Rack-mounted or tower-type servers such as HP, DELL, and IBM are
recommended.
The Dell Power Edge R320 server is recommended when the NEs are less than 5000. The
specific configuration parameters are as follows:
Table 1-1 Specific configuration parameters of the Dell Edge R320 server
Item Description
Central Intel Xeon E5-2407 2.20GHz, 10M Cache, 6.4GT/s QPI, No
Processing Unit Turbo, 4C, 80W, Max Mem 1066MHz
Main memory 4GB RDIMM, 1600 MT/s, Low Volt, Single Rank, x8 Data Width
Cache memory 2.5MB per core
Hard Disk 2x 500GB 7.2k RPM SATA 6Gbps Entry 3.5in Cabled Hard Drive
capacity
2 PCIe slots:
One x8 PCIe slot with x4 bandwidth, half-length, half-height
Expansion Slot One x16 PCIe slot with x16 bandwidth, half-length, full-height

Raisecom
LAN Broadcom 5720 Dual Port 1Gb LOM

Communication
interfaces
SW RAID 1 for S110 (2 SATA HDDs) with Cabled Chassis
Backup device S110, Software RAID (for Microsoft OS Only)
Power Supply Dual, Hot-plug, Redundant Power Supply, 350W
Monitor Dell UltraSharp 24 Monitor, U2412M, 24"
The Dell Power Edge R630 server is recommended when the NEs are more than 5000 but less
than 20000. The specific configuration parameters are as follows:
Item Description
Central 2x Intel Xeon E5-2603 v3 1.6GHz,15M Cache,6.40GT/s QPI,No
Processing Unit Turbo,No HT,6C/6T (85W) Max Mem 1600MHz
Main memory 2x 4GB RDIMM, 2133MT/s, Single Rank, x8 Data Width
Hard Disk 2x 500GB 7.2K RPM SATA 6Gbps 2.5in Hot-plug Hard Drive
capacity
slot 1: Half length, half height - PCIe 3.0 x16
slot 2: 3/4 length, full height - PCIe 3.0 x16
Expansion Slot Dedicated RAID card slot
LAN Broadcom 5720 QP 1Gb Network Daughter Card
Communication
interfaces
RAID 1 for S130
Backup device S130, Software RAID
Power Supply Dual, Hot-plug, Redundant Power Supply (1+1), 495W
The Dell Power Edge R820 server is recommended when the network units are more than
20000 but less than 50000. The specific configuration parameters are as follows:
Item Description
Central 4x Intel Xeon E5-4620 2.20GHz, 16M Cache, 7.2GT/s QPI, Turbo, 8
Processing Unit Core, 95W, Max Mem 1333MHz
Main memory 2x 8GB RDIMM, 1600MT/s, Low Volt, Dual Rank, x8 Data Width

Raisecom

Hard Disk 2x 600GB 10K RPM SAS 6Gbps 2.5in Hot-plug Hard Drive
capacity
7 PCIe slots:
Two x16 half-length, full-height
One x8 half-length, full-height
Three x8 half-length, half-height
Expansion Slot One x8 half-length, full-height for the RAID controller
LAN Intel Ethernet I350 QP 1Gb Network Daughter Card
Communication
interfaces
RAID 1 for H710P/H710/H310
Backup device PERC H710 Adapter RAID Controller, 512MB NV Cache
Power Supply Dual, Hot-plug, Redundant Power Supply (1+1), 750W
When the NMS is installed or upgraded, it will automatically calculate the minimum
disk space. If the disk space is insufficient, the system will pop up an insufficiency
prompt, causing the installation or upgrade failure.
The usability of servers

Adopt RAID to realize data backup. RAID1 is recommended.
Adopt hot swapping redundancy power supply to make the use of the power supply
redundancy backup available.
Adopt hot swapping hardware to facilitate capacity expansion.
Purchase Raisecom dual-server hot-backup HA solution to be disaster tolerant in
different areas.
1.3.2 Operation system requirements
In Windows Server family OSs and Windows7 or later OS, 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.

Raisecom
Supported OSs
Table 1-4 lists OSs supported by the NView NNM system. For a PC where the NView NNM
system is installed, its architecture and OS should be matched. The 32-/64-bit architecture
should be installed with 32-/b4-bit OS. Otherwise, installation fails.
Table 1-4 Supported OSs
Classification 32-bit OS 64-bit OS

Windows Server 2003 SP2 Windows Server 2003 SP2
NView NNM
network Standard X86 Standard X64
Windows Server 2003 SP2 Windows Server 2003 SP2
management
service Enterprise X86 Enterprise X64
Windows XP SP3 Professional Windows Server 2008 R2
X86 Standard X64

Windows Server 2008 R2
Enterprise X64
Windows XP SP2 Professional Windows XP SP2 Professional
NView NNM
distributed X86 X64
Windows XP SP3 Professional Windows 7 SP1 Professional X64
performance
X86 Windows 7 SP1 Enterprise X64
monitoring
Windows 7 SP1 Professional Windows 7 SP1 Ultimate X64
service
X86 Windows Server 2003 SP2
NView NNM Windows 7 SP1 Enterprise Standard X86

distributed X86 Windows Server 2003 SP2
Clients Windows 7 SP1 Ultimate X86 Enterprise X86

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

Windows Server 2003 SP2 Windows Server 2008 R2
Enterprise X86 Enterprise X64
Standard or Enterprise is recommended for the server and distributed performance

monitoring service.
Professional or Ultimate is recommended for distributed clients
The operating system should be in English or Chinese. Do not install the NView NNM
on an OS based on other languages such as Spanish or Portuguese
We recommend that the NMS Server and distributed PM service use the
Standard/Enterprise OS.
We recommend that the distributed NMS Client uses the Professional/Ultimate OS.
Only English OS is supported. Do not install the NView NNM system on the OS 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.

Raisecom
Requirements on user privileges of OS

When the NView NNM system runs on the Windows Server family OS and Windows7 or
later OS, you should bring some requirements on user privileges of the OS.
Table 1-5lists requirements on user privileges of the OS for installing, upgrading, and starting
the NView NNM system.
Table 1-5 Requirements on user privileges of OS
Classification Privilege requirement

Install/upgrade/start the Users, who log in to the OS, must have the administrator
NView NNM system privilege.
locally We recommend using the administrator account to
install/upgrade/start the NView NNM system locally.
Install/upgrade/start the Users, who log in to the OS, must belong to the
NView NNM system Administrators group and Remote Desktop Users group
remotely simultaneously.
If the user does not belong to either of the 2 groups,
operation may fail.
User privileges of PM service OS must be identical to the ones of NMS Server OS.
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

13306: NView NNM Interface 13306 (NView NNM
Normal use Database/3
database database) must be enabled.
Interface 13303 must be
13308: the PM service
database of the NView NNM enabled if you use iTN remote
zero-configuration.
13303: iTN zero- Interface 13308 must be
configuration database enabled if you use
performance distributed
deployment.

Raisecom

61616: inter-process service
Message bus/2 They must be enabled.
interface
61617: intra-process service
interface
9302: event channel
InstanceServer service/2 They must be enabled.
9304: command channel
9362: intranet interface of the
RMI/3 They must be enabled.
resource model
9367: extranet interface of
the resource model

9364: management interface
of the resource model

9320: DCServer command
Data center/3 You do not need to enable them
channel interface unless you wish to use the data
9322: DCEMS command
center.
channel interface
9323: DCEMS event channel
interface
9312: upgrade service
Upgrade tool/5 They must be enabled.
command channel
9314: upgrade service event
channel
9303: upgrade tool command
interface
9304: upgrade tool event
interface
9307: downloading the
upgrade package through

HTTP
Device discovery and 16262: enabling the device It must be enabled.
polling/1 discovery and polling.
16261: MSG NAT traversal You do not need to enable
Channel traversal/102
18080: Relay service them.
interface of WEB traversal Transport devices: you must
1808118180: Web Agent enable interface 16262 when
service interface pool of you use iTN remote NAT
WEB traversal traversal.
Other interfaces must be
enabled if you use enterprise

gateways.
514: syslog You must enable these
Standard protocol stack/8
161and 162: SNNP interfaces. You can enable
23: Telnet them based on functions to be
22: SSH used,
21: FTP You must enable interface 67
69: TFTP if you wish to use the device
67: DHCP deployment service.
9400: InstanceServer
JMX debugging interface At present, only interface 9400
9401: Client
/4 (InstanceServer) must be
9408: DCEMS
enabled. You can enable other
9409: DCServer
interfaces if required.

Raisecom

9317: northbound interface
Northbound CORBA/3 You do not need to enable the m
interface service process unless you wish to use the
9315: naming service process
CORBA northbound interface
9316: notification service
of a transport device.
process
9381: RAW
TL1/2 You do not need to enable the m
9382: Telnet
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.
9336: Socket forwarding
Alarm forwarding/2 You do not need to enable them.
162: Trap PDU forwarding Enable the related interface if
you wish to use Socket
forwarding or Trap PDU
forwarding.
Debugging JConsole 1099: debugging interface You do not need to enable the
tool interface unless you wish to
debug the system.
29001: server internal
Dual-server Dual-server Warm- You do not need to enable them
Warm- standby program/7 communication unless you wish to use dual-
29002: data transmission
standby server Warm-standby.
29003: alarm
synchronization/HTTP
communication
29004: disk Agent
communication
29005: mirroring driver
communication
29006: heartbeat detection
29007: client service
communication
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

Raisecom
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, uninstall 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 OS 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.
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 kernel V5.4.4 on the PC where the NMS Server is installed.
Step 2 Install the PM service on a PC installed with NMS Server or on the distributed PC.
Step 3 Upgrade the EMS through the upgrade package.
Step 4 In performance distributed deployment mode, upgrade the NMS Server in advance, and
enable the PM service on the distributed PC to upgrade automatically.
Step 5 To management devices through multiple NMS Clients, install the NMS Client at the NMS
Client PCs. The NMS Client is automatically upgraded after the NMS Server is upgraded
successfully. Or, upgrade the EMS through the upgrade package.
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 FILE, upgrade package, and License file to the local hard-disk of the PC.

Raisecom
Table 1-7 Preparing files
Program License file

The installation FILE of NView License file matching with versions of the
NNM kernel V5.4.4 NView NNM kernel V5.4.4 and EMS
EMS upgrade package matching of
the device
(Optional) the installation FILE of
NMS Client
(Optional) the PM service installation
FILE of the NView NNM
The NView NNM kernel V5.4.4 provides specified NMS Client installation program,
which is of small size and is suitable for installing the NMS Client independently.
The NView NNM kernel V5.4.4 provides the specific PM service installation file,
which is used on the centralized and distributed PCs which need to be installed with
the PM service.

Raisecom
NView NNM (V5) Installation Guide 2 Installation steps
2 Installation steps
This chapter describes how to install the NView NNM system, including the following
sections:
Installing NView NNM system
Install green version NMS Client
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 and NMS Client by following
these steps. For details about how to install the centralized PM service, see section 2.4
Installing distributed PM service.
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.4 Installing distributed PM service.
For a PC where the NView NNM system is installed and then is uninstalled, you
need to delete the original installation file before re-installing the NView NNM
system. The original network management data will be uninstalled and cannot be
restored after you delete the installation file. Therefore, copy the whole installation
file and keep it well before uninstalling it. Perform this operation with care.
During installation, the system checks the installation path. If there is any
undeletable file, a prompt appears and the system exits the installation progress.
Before re-install the NView NNM system, delete the original installation file.
Step 1 Double-click the NView NNM installation FILE 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
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 Install the NMS Server, NMS Client, and
NMS Server. NMS Control if you select this radio
button.
By default, this radio button is selected.
Client Be installed with the Install the NMS Client if you select this
NMS Client. radio button.

Raisecom
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
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
Client, you need to enter the IP address of the public network. When NMS Client, which
is in the public network, accesses to 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
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
Figure 2-6 Confirming installation information

Raisecom
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
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 OS, as shown in Figure 2-9.
Figure 2-9 Start menu (1)
2.2 Install green version NMS Client

The green version NMS Client does not need installation FILE. You only need to copy or
download the archive to the local disk on the host, and decompress the archive. In the aspects
of functions and upgrade, the green version NMS Client is the same with the ordinary Client.
Installation steps are shown as below.
Make the archive of the green version NMS Client after the Server is installed and
upgraded.
Copy or download the archive.
Decompress the archive to the local disk on the PC installed with NMS Client.

Raisecom
(Optional) create a shortcut for the green version NMS Client on the desktop.
Delete the whole directory of the green version Client to complete uninstallation.
2.2.1 Make an archive

Make an archive for the green version NMS Client matched with the current NMS. Later use
this archive to install the green version NMS Client.
Step 1 On a server, double-click the script file. By default, the installation path is
C:\NMS\PLATFORM\NNM5\upackage\NMS_Client_Green.bat.
Step 2 The command line window appears, where the script is automatically executed, as shown in
Figure 2-10.
Step 3 After the command line window disappears automatically, the archive is made in the directory
of the script file, as shown in Figure 2-11. The example for the file name as below.
NMS_Client_Green_20150527_win32.zip and NMS_Client_Green_20150527_win64.zip,
related to 32-bit and 64-bit OSs.
Figure 2-10 Command line window

Raisecom
Figure 2-11 Example for archive file
2.2.2 Installation
Put the archive to the local disk in advance, and decompress it. You can copy the archive or
download the archive from the server through the network.
Copy archive
According to the NMS Client OS, copy the 32-bit or 64-bit archive to the local disk on the
client, by using portable hard disk.
Download archive through the network

On the client, browse and visit the http:// IP address of the server:9307. Files are displayed on
the page, select the record of archive to be downloaded, and click Download to save the file
to the local disk.
Archive
The path where the archive is to be decompressed cannot include blank space.
The archive is in the form of ".zip". Right-click the archive, select the decompressing
menu corresponding to the archive file, and decompress the file to the local disk. In
this case, NMS Client is installed.
If the root directory to decompression is C:\NMSGreen, after the archive is
decompressed, the directory of the start program to the Client is
C:\NMSGreen\NNM5\client\RunClient.exe.
If the root directory to decompression is C:\NMSGreen, after the archive of the

green version Client is decompressed, the path of start program for upgrade tool
is C:\NMSGreen\um\utool\RunUpgrade.exe.

Raisecom
If the server is upgraded later, you can use the green version NMS Client matched
with the Server by making, copying/download and decompressing archive, and
you also can upgrade Client automatically or manually through the upgrade tool.
Upgrade NMS Client manually by using the start program for upgrade tool only.
2.2.3 (Optional) create shortcut on the desktop

Creating a shortcut of the green version NMS Client on the desktop is convenient to start the
NMS Client on the desktop.
If the root directory to decompression is C:\NMSGreen, after decompressing the archive of
the green version NMS Client, the path of start program for upgrade tool is
C:\NMSGreen\NNM5\client\RunClient.exe.
Step 1 Right-click RunClient.exe, select Send To/Desktop (create shortcut). Figure 2-12 shows the
shortcut icon on the desktop.
Step 2 (Optional) right-click the shortcut icon, select Rename to modify the name.
Figure 2-12 Shortcut icon of Client on the desk
2.3 Installing NMS Client
Only when you need to use other PCs to manage devices, you can install NMS
Clients on them. Installing and upgrading the green version NMS Client is more
flexible.
The NMS Client can be installed in 2 modes. In these 2 modes, the operation steps
and interfaces are identical while installation FILEs are different.
Installing the NMS Client through the independent NMS Client installation FILE:
distributed NMS Client is installed through the independent NMS Client installation
FILE.
Installing the NMS Client through the NView NNM installation FILE: the NView NNM
installation FILE is a complete set, which supports installing the NMS Client.
Installing NMS Client through independent NMS Client installation FILE

Step 1 Double-click the NView NNM installation FILE.
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\.

Raisecom
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.
is in the public network, access the NMS Server, they need the NAT-translated IP address
or the one of the public NIC.
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 OS, as shown in Figure 2-13.
Installing NMS Client through NView NNM installation FILE

Step 1 Double-click the NView NNM installation FILE.
Step 4 Click Next and then select the Install NMS Client.

Raisecom
Step 5 Click Next and then select the installation path of the NMS Client. By default, it is
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.
Step 7 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.
is in the public network, access the NMS Server, they need the NAT-translated IP address
or the one of the public NIC.
Step 9 Click Next.
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 OS, as shown in Figure 2-14.

Raisecom
2.4 Installing distributed PM service
Install the PM service automatically in performance distributed deployment mode only.

The PM service can be installed on multiple PCs, in the large-scale network,
distributed deployment improves PM capability.
The PM service also can be installed on the PC installed with NMS Client, in the
small-scale network or on the Server, promote the PM ability through centralized
deployment.
The example for the installation name of distributed PM service is as below.
NView_NNM_PM_V5_20140603_win32.exe
Step 1 Double-click the Installation FILE of the distributed PM service.
Step 4 Click Next and then select the installation path of the PM service. By default, it is
D:\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 6 (Suitable for distributed deployment only) click Next and then enter the IP address of the
NMS Server.
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.
: be used to start the NMS Control.

Raisecom
In centralized deployment mode, the PM service provides start menu to uninstall the program
only, namely, Start/ NMS_PM/Uninstall. Executing other functions through the start menu on
the NView NNM.
On a PC with performance distributed deployment, the start shortcut of the PM Server will be
automatically added to the Start menu of the Windows OS, as shown in Figure 2-15.
Figure 2-15 Start menu on the PC with performance distributed deployment
2.5 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 Client 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 Client manually, follow these
steps.
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.
After NMS Server is upgraded, you can re-make and re-install the green version
NMS Client, namely, upgrade the distributed Client.
For details about how to upgrade distributed NMS Client and PM Server automatically
and the upgrade tool, see NView NNM (V5) Upgrade Guide.
Step 1 Double-click the Upgrade shortcut to start the upgrade tool.
Step 2 Click Please specify the upgrade package. A dialog box appears. Select the local upgrade
package.
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-16 shows
the prompt contents after upgrade.

Raisecom
Figure 2-16 Upgrading the NView NNM system successfully

Raisecom
NView NNM (V5) Installation Guide 3 Starting configurations
3 Starting configurations
This chapter describes how to configure the NView NNM system to be started automatically
with the OS and how to start services of the NView NNM system, including the following
sections:
Configuring NView NNM to be started automatically with OS
Configuring services to be started automatically with NView NNM system
3.1 Configuring NView NNM to be started automatically

with OS
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 OS 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 OS, 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
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 OSs, 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 Uninstalling NView NNM system
4 Uninstalling NView NNM system
This chapter describes how to uninstall the NView NNM system, including the following
sections:
Uninstall NMS Server or Client
Uninstall PM service
4.1 Uninstall NMS Server or Client

You can uninstall the NMS Server or Client when it is not required.
To uninstall the NView NNM system, stop it (including the NMS Server and NMS Client) in
advance. When you uninstall 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
uninstall the NView NNM system, follow these steps:
We recommend backing up configurations of the NView NNM system manually

before uninstalling 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.
After uninstallation, all the data of the NView NNM system are cleared. Perform this
operation with care.
In centralized deployment mode, this operation uninstalls the NMS Server and Client
at the same time; in distributed deployment mode, uninstall the NMS Client on a
distributed PC.
For the green version NMS Client, delete installation file directly to complete
uninstallation.
Step 1 To uninstall the NView NNM system through the Windows OS, choose Start > All
Programs > NMS > UnInstall NMS, as shown in Figure 4-1.

Raisecom
Figure 4-1 Menus for uninstalling the NView NNM system
Step 2 (Optional) to uninstall the NView NNM system through the Control Panel of the Windows
OS, choose Start > Control Panel > Add or Remove Programs, select the NMS record, and
then click Remove, as shown in Figure 4-2.
Figure 4-2 Removing the NView NNM system through the Control Panel
Step 3 A dialog box appears, as shown in Figure 4-3.

Raisecom
Figure 4-3 Removing the NView NNM system
Figure 4-4 Confirming the removal operation

Raisecom
Step 5 Click Yes. The system begins to uninstall the NView NNM system.
Step 6 After uninstallation, the system prompts you to restart the PC, as shown in Figure 4-5.
Figure 4-5 Prompting to restart the PC
Step 7 Click Finish and the PC will be restarted.
4.2 Uninstall PM service

The PM service supports the independent uninstallation menu, from which uninstall the PM
service and related performance data, thus having no influence on other functions of the NMS.
Step 1 Uninstall the PM service in the start menu of Windows. Select Start > Program >
NMS_PM > Uninstall.
Step 2 The Uninstall PM page appears. Click Next. A dialog box appears for you to confirm whether
the PM service is to be uninstalled.
Step 3 Click Yes. The system begins to uninstall the PM service.
Step 4 After uninstallation, the system prompts you to restart the PC.
Step 5 Click Finish and the PC will be restarted.

Raisecom
NView NNM (V5) Installation Guide 5 FAQ
5 FAQ
This chapter describes some questions encountered during installing and uninstalling the
NView NNM system.
5.1 How to stop SNMP Trap service of Windows OS?

On a PC, where the NView NNM system is installed, the SNMP Trap Service of the Windows
OS should be stopped. To stop the SNMP Trap Service of the Windows OS, 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 OS, the SNMP Trap Service is started by default. This
service occupied interface 162. Before installing the NView NNM system on this OS,
stop the SNMP Trap Service. Otherwise, the NView NNM system fails to receive alarms.
This requirement is designed for the PC where the NMS Server in installed. It is not
required for PCs where the NMS Client is installed.

Raisecom
In general, interfaces for the NView NNM system include interfaces 93039336 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 Client 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 installed with NMS Server,
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 installed
with NMS Server.
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.
Confirm whether the PC starts firewall. Since starting firewall will cause connection
failure, connect the NMS Client to NMS Server after close firewall.

Raisecom
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 is working 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 (United States) from the drop-list menu at the Regional Options tab, as shown
below.

Raisecom
Step 3 Choose English (United States) from the drop-list menu at the Advanced tab as below.

Raisecom
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
OSs do not provide this file. Therefore, prompt boxes will appear, as shown below:
Figure 5-1 Prompt box (1)

Raisecom
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
This problem will not happen to supported OSs listed in this guide. It happens when
you install the NView NNM system for an untested OS. When the problem is resolved,
we cannot ensure that the NView NNM system will work properly. Therefore, we
recommend installing OSs supported by the NView NNM system.

Raisecom
NView NNM (V5) Installation Guide 6 Appendix
6 Appendix
This chapter describes terms and abbreviations involved in this guide, including the following
sections:
Terms
Abbreviations
6.1 Terms
A
Traps that are sent when the device or the NView NNM system detects a
Alarm
fault.
C
The customer uses services provided by the device. The customer
Customer information can be attached with the NE or alarm. The customer
information is saved in the NView NNM system only.
D
In the NView NNM system, the data center is an auxiliary program. It
Data center backs up and upgrades the system software and configuration files of the
devices and maintains their versions.
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,
Data dump
historical alarms, performance collection data, and system monitoring
collection data.
It can be used to scan devices in the IP address range and add them to the
Device scan
NView NNM system.
The domain takes the NE as the minimum granularity. It refers to
Domain
collection of resources that can be operated by users.

Raisecom
E
Each NE can be converted in to the equivalent NE based on its equivalent
Equivalent NE 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
It refers to the authorization file of the NView NNM system. The License
License
file defines network management functions available for users.
N
Network
The device is managed as the NE in the NView NNM system.
element
Auxiliary program of the NView NNM system. It can manage all service
NMS Monitor 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.
It is an interface program between the NView NNM system and the upper
Northbound
network management system. The upper network management system
interface
can manage devices through the northbound interface.
O
Operate Authority used to operate and manage the NView NNM system and its
privilege resources
P
Performance The NView NNM system collects and displays the traffic or packet loss
monitor rate of devices.
Polling It can be used to periodically detect whether the device is offline.

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

Symbol
can display the network topology better.
With synchronization, the NView NNM system can update device
Synchronization 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
Graphical network topology in the NView NNM system. It displays the
Topology networking application, alarms generated on subnets or NEs, and status
of nodes.
The mode for a device sending alarms to the NView NNM system. It is
Trap
sent to the NView NNM system through the SNMP packet.
U
The NMS Client user and the domain and operation privilege of the user
User and its user group define the network management functions available for
the user.
The user group can provide identical domain and operation privilege for
User Group
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

Raisecom
NMS Network Management System

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: export@raisecom.com

NView NNM (V5) Installation Guide (Rel - 46)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

NView NNM (V5) Installation Guide (Rel - 46)

Hochgeladen von

Copyright:

Verfügbare Formate

www.raisecom.

NView NNM (V5)

is the trademark of Raisecom Technology Co., Ltd.

Product name Version

Indicates a potentially hazardous situation that, if not avoided,

Raisecom Proprietary and Confidential

Times New Roman Normal paragraphs are in Times New Roman.

Raisecom Proprietary and Confidential

Raisecom Proprietary and Confidential

Raisecom Proprietary and Confidential

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

2 Installation steps ......................................................................................................................... 22

3 Starting configurations .............................................................................................................. 38

4 Uninstalling NView NNM system .......................................................................................... 40

Raisecom Proprietary and Confidential

Raisecom Proprietary and Confidential

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

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

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

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

Figure 1-8 Deploying NMS Client in dual-NIC environment .............................................................................. 12

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

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

Figure 2-1 License agreement .............................................................................................................................. 23

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

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

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

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

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

Figure 2-7 Installation file .................................................................................................................................... 28

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

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

Figure 2-10 Command line window ..................................................................................................................... 30

Figure 2-11 Example for archive file ................................................................................................................... 31

Figure 2-13 Start menu (2) ................................................................................................................................... 33

Figure 2-14 Start menu (3) ................................................................................................................................... 34

Figure 2-16 Upgrading the NView NNM system successfully ............................................................................ 37

Raisecom Proprietary and Confidential

Figure 4-4 Confirming the removal operation ...................................................................................................... 42

Figure 4-5 Prompting to restart the PC ................................................................................................................ 43

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

Raisecom Proprietary and Confidential

Table 1-5 Requirements on user privileges of OS ................................................................................................ 17

Table 1-6 Interface requirements .......................................................................................................................... 17

Table 1-7 Preparing files ...................................................................................................................................... 21

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

Raisecom Proprietary and Confidential

1 Preparing for configurations

Installation and deployment modes of NMS Server

Raisecom Proprietary and Confidential 1

Figure 1-1 Centralized deployment

Performance distributed deployment mode is not required if you do not need to

Raisecom Proprietary and Confidential 2

Figure 1-2 Performance distributed deployment

Installation and deployment modes of NMS Client

Descriptions about installation files

Raisecom Proprietary and Confidential 3

Raisecom Proprietary and Confidential 4

During network management, it is crucial to provide continuous network management

1.2 System deployment

1.2.1 Introduction to system program

NMS Server program

Raisecom Proprietary and Confidential 5