NetMaster Installation Guide

NetMaster NMS
Installation Guide
December 2015
Release: R14B00 Rev A
Copyright 2015 by Ceragon Networks Ltd. All rights reserved.

NetMaster NMS R14B00 Installation Guide
Notice
This document contains information that is proprietary to Ceragon Networks Ltd. No part of this
publication may be reproduced, modified, or distributed without prior written authorization of
Ceragon Networks Ltd. This document is provided as is, without warranty of any kind.
Trademarks
Ceragon Networks, FibeAir and CeraView are trademarks of Ceragon Networks Ltd., registered
in the United States and other countries.
Ceragon is a trademark of Ceragon Networks Ltd., registered in various countries.
CeraMap, PolyView, EncryptAir, ConfigAir, CeraMon, EtherAir, CeraBuild, CeraWeb, and
QuickAir, are trademarks of Ceragon Networks Ltd.
Other names mentioned in this publication are owned by their respective holders.
Statement of Conditions
The information contained in this document is subject to change without notice. Ceragon Networks
Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in
connection with the furnishing, performance, or use of this document or equipment supplied with it.
Open Source Statement

The Product may use open source software, among them O/S software released under the GPL or
GPL alike license ("Open Source License"). Inasmuch that such software is being used, it is released
under the Open Source License, accordingly. The complete list of the software being used in this
product including their respective license and the aforementioned public available changes is
accessible at:
Network element site:
ftp://ne-open-source.license-system.com
NMS site:
ftp://nms-open-source.license-system.com/
Information to User
Any changes or modifications of equipment not expressly approved by the manufacturer could void
the users authority to operate the equipment and the warranty for such equipment.
Revision History
Rev Date Author Description Approved by Date
A December 2015 Yael Klein NetMaster release Moti Sharf December 2015
R14B00
Ceragon Proprietary and Confidential Page 2 of 105

Table of Contents
1. About NetMaster ............................................................................................... 4
2. NetMaster Installation....................................................................................... 6
2.1 NetMaster Installation on Windows ................................................................................ 6
2.1.1 NetMaster Server Pre-Installation for Windows ............................................................. 6
2.1.2 NetMaster Installation for Windows ................................................................................ 6
2.1.3 System Manager Installation on Database Server ....................................................... 19
2.1.4 Uninstall NetMaster for Windows ................................................................................. 29
2.2 NetMaster Installation on Solaris ................................................................................. 31
2.2.1 NetMaster Server Pre-installation for Solaris ............................................................... 31
2.2.2 NetMaster Server Installation for Solaris ...................................................................... 32
2.2.3 Uninstall NetMaster for Solaris ..................................................................................... 34
2.3 Post Installation ............................................................................................................ 35
2.3.1 NetMaster Server post installation ............................................................................... 35
2.4 Database Installation .................................................................................................... 41
2.4.1 NetMaster Database .................................................................................................... 41
2.4.2 Oracle ........................................................................................................................... 42
2.4.3 PostgreSQL .................................................................................................................. 47
2.5 High Availability Solution .............................................................................................. 60
2.5.1 NetMaster High Availability Solution ............................................................................ 60
2.5.2 Installation Instructions ................................................................................................. 64
2.5.3 Failover Procedure ....................................................................................................... 67
2.5.4 System Parameter Configuration ................................................................................. 68
2.5.5 Troubleshooting ............................................................................................................ 71
2.5.6 High-Availability Solution for Solaris ............................................................................ 78
2.6 External Documents ................................................................................................... 100
2.6.1 System Requirements ................................................................................................ 100
2.6.2 Technical Description ................................................................................................. 100
3. Migration from PolyView to NetMaster ........................................................ 101

3.1 Overview..................................................................................................................... 101
3.2 Importing Topology from PolyView to NetMaster ....................................................... 101
3.2.1 Step 1: Create a PolyView Export File ....................................................................... 101
3.2.2 Step 2: Prepare for Import into NetMaster ................................................................. 102
3.2.3 Step 3: Run the Topology Import Tool ....................................................................... 102
3.2.4 Step 4: View Import Results ....................................................................................... 103
3.3 Importing users from PolyView to NetMaster ............................................................. 104
3.3.1 Step 1: Export PolyView User Definitions to a File .................................................... 104
3.3.2 Step 2: Import the User Definitions into NetMaster .................................................... 104

1. About NetMaster
NetMaster is a comprehensive Network Management System offering centralized
operation and maintenance capability for a range of network elements.
NetMaster offers full range management of network elements. It has the ability to
perform configuration, fault, performance and security management. NetMaster is
the user interface to transmission and access products and the key issue for the
system is to present management networks in the simplest possible manner. The
software has network auto-discovery and uses the configuration data in the
network elements to automatically build the managed network. The various
elements and their attributes may be accessed using the intuitively graphical
presentation of the element and its components. NetMaster has a continuously
updated display of network status and network events are reported from the
elements using notifications. An extensive database and context sensitive help
facilities enable the user to analyze and report network events.
NetMaster provides the following network management functionality:
Fault Management
Configuration Management
Performance Monitoring
Security Management
Graphical User Interface with Internationalization
Network Topology using Perspectives and Domains
Automatic Network Element Discovery
HW and SW Inventory
Software Download jobs
Northbound interface to higher order OSS
Report Generator
Functionality is maintained during network growth, with solutions covering the
entire range of radio networks from a single hop to nationwide multi-technology
networks. High availability and reliability is obtained through various redundancy
schemes.
NetMaster functionality
The NetMaster system is scalable both in size and functionality. The NetMaster
NMS Server is the basis for any NetMaster system, providing basic functionality
within the Fault, Configuration, Performance and Security (FCPS) management
areas. The NMS Server is by itself an advanced tool for the user to perform
operations and monitor network elements for the whole operational network in
real time. The flexible client/server architecture gives the operators easy access to
all network elements and full control of the system from many different locations.
By selecting among a set of optional features, the NetMaster system can be
enhanced and tailored to each operators individual needs and requirements. With

all optional features installed, the NetMaster system provides the operator with an
advanced and sophisticated network management system that will highly increase
the efficiency of operations and maintenance in the network.
For easy integration to external higher-level management systems, a Northbound
SNMP interface can be provided.
Installation Guide
The NetMaster NMS Installation Guide is the printed version of installation section
of the online help system for the NetMaster network management system. The
installation guide can provide you with help about how to install and how to
configure the application. For detailed information regarding how to use
NetMaster, including system management information, please see the NetMaster
NMS User Guide.
More information
If you cannot find the answer to your question in the installation manual, contact
your responsible support person.

2. NetMaster Installation
2.1 NetMaster Installation on Windows
2.1.1 NetMaster Server Pre-Installation for Windows
Prepare Database
NetMaster Server requires a database to work. Make sure that a database server is
installed and reachable from the computer on which you want to install NetMaster
Server.
The database server can be installed on the same computer as the NetMaster
Server refer to the NetMaster System Requirements document for guidance.
However, it does not need to be installed on the same computer.
If the database server is running on a different computer than the NetMaster
Server, the firewall settings on the database server may have to be modified (i.e.
open the port used for communication with the database server).
Oracle and PostgreSQL database servers are supported see the NetMaster
System Requirements document for information about supported database
editions.
See How to install PostgreSQL if you need to install a database server from
scratch. Please refer to Oracle documentation for instructions how to install
Oracle.
If NetMaster is currently using a PostgreSQL version older than PostgreSQL 9.1.3
see PostgreSQL database upgrade on how to upgrade to the 9.1.3 version.
Note that these pre-installation steps are not required for NetMaster Client or the
Northbound SNMP Agent installations.
2.1.2 NetMaster Installation for Windows

The following chapter guides you through NetMaster installation on Windows
platform.
This guide requires that the steps for NetMaster Server Pre-Installation for Windows
already have been completed.

NetMaster Install Sets

NetMaster allows you to install any of the following install units:
Install Unit Explanation

Client NetMaster Client. Can be installed on a separate machine. Also available for
Solaris platform, see NetMaster Client installation for Sun Solaris for details.
Server NetMaster Server.
System Manager Configuration and maintenance tool for NetMaster Server. System Manager
must be installed on both the NetMaster Server and the database server.
SNMP Agent Northbound interface to higher-order network management systems
Polyview Topology Enables exporting discovered elements and subnetworks from PolyView
Import into a file and then importing them, while preserving their hierarchy, into
NetMaster as managed elements in administrative domains
All install sets:
Install Set Explanation

Client NetMaster Client only.
Server NetMaster Client, NetMaster Server, SNMP Agent, System Manager and
Polyview Topology Import
System Manager System Manager only. Intended for stand-alone database server installation.
Custom Pick one or more of all available install units.
Install Modes
There are three modes of installation:
New Installation
Upgrade Installation
Maintenance Installation
The NetMaster installer looks for existing NetMaster installations on your
installation server in order to determine correct install mode.
2.1.2.2 New installation

If no existing NetMaster installation is detected on the computer, the installer will
run in New Installation mode.
You may cancel the installation at any step until the wizard starts installing the
files.

Run the Setup.exe file to launch the NetMaster Installer home page.
Click Install NetMaster to initiate NetMaster installation. A File Download
Security Warning pop-up window appears.
Click Run to continue installation. An Internet Explorer Security Warning pop-up

window appears.
Click Run to continue installation.

The Installer prepares to start:
Proceed by following the Installation wizard as follows:
Installation wizard in New installation mode

The Introduction step displays some general information about the installation
process.
Click Next to continue the wizard.

Read the license agreement.
If you accept the agreement, select the Accept option and then click Next to
continue.

Choose Install Set step. Note that the NetMaster Server install sets include Server,
System Manager, Client and Northbound SNMP Agent.
\
Click Next to continue.

Choose Install Set step - Custom. This step is only displayed if the "custom"
install set is selected in the previous step.
In this step you can select each component individually. See the Description field
for information about the selected component.
Press Next to continue.

Choose Install Folder step.

In this step you can choose where on the file system to install the software.

Choose Shortcut Folder step.

In this step you can choose where to place product icons/shortcuts. Note that
there is an option for creating icons for all Users

Pre Installation Summary step

This step gives an overview of the current selections.
Installing step
Watch the product features being presented during the installation progress.

Install Complete step.

If there were any problems encountered during the installation, see the
installation log file located in the installation destination folder for details.
Click Done to finish the wizard. The installation wizard configures the system
when completing the wizard.

If included in the installation set, System Manager can be opened at the end of
installation:
Click Yes to open System Manager, and complete configuration of NetMaster,

including importing a license, connecting NetMaster to a database, scheduling
database backup and setup mail parameters.
If NetMaster Server is installed, the server will be installed as an automatic
Windows Service, with its own Server monitor in the systray. The NetMaster
Server monitor starts when installation is completed, and you are prompted
whether to start the NetMaster Server. If you don't want the NetMaster Server to
start automatically upon computer reboot, you can set the mode of the NetMaster
Service to manual in the Services applet in the Control Panel.
Proceed with the NetMaster Post installation steps.
2.1.2.3 Upgrade installation

If the installer detects an older version of NetMaster installed on the computer,
the installer will run in Upgrade mode. In this mode you will be able to upgrade
the existing components and also to reselect which components to be installed on
the computer. The existing installation will be uninstalled and replaced with the
components selected in this maintenance installation. Note that existing
components not selected will be uninstalled.
NetMaster System Manager can be launched after the NetMaster software
installation and gives options to upgrade or reset the NetMaster database.

Note: Action permissions for new functionality are default disabled

for all user groups; these must be specifically granted for user
groups needing access.
If this is an upgrade from an older version of NetMaster, using
PostgreSQL 8.3, the PostgreSQL database must be upgraded to
version 9.1 for the maintenance tasks to work properly. See
PostgreSQL database upgrade.
The netmaster_environment.cmd file will be generated however
the database administration user and password will be left
empty.
Most of the installation steps are identical to the New Installation mode:
Introduction step informs that a previous version of NetMaster is detected,
and displays some information about the detected installation.
License Agreement step is omitted in upgrade installations.
Choose Install Items step this step initially displays the components
detected in the existing NetMaster installation. In this step you can select
which components to be installed on the computer. Note that if you deselect
existing components, those will be uninstalled.
Choose Install Folder and Choose Shortcut Folder steps omitted in
upgrade installations. The installer will use the folders detected from the
previous installation.
Pre Install Summary step gives an overview of the current selections.
Installing step watch the product features being presented during the
installation progress.
Installation Summary same as in new installations.
2.1.2.4 Maintenance installation

If the installer detects an existing NetMaster installation with the same version,
the installer will run in Maintenance mode. In this mode you will be able to
reselect which components to be installed on the computer. The existing
installation will be uninstalled and replaced with the components selected in this
maintenance installation. Existing components not selected will be uninstalled.
NetMaster System Manager can be launched after the NetMaster software
installation and gives the option to reinitialize the NetMaster database.
Most of the installation steps are identical to the New Installation mode:
Introduction step informs that an existing installation is detected, and
displays some information about the detected installation.
Choose Install Items step this step initially displays the components
detected in the existing NetMaster installation. In this step you can select
which components to be installed on the computer. Note that if you deselect
existing components, those will be uninstalled.
Installation Summary - same as in new installations.

Installing step the existing NetMaster installation will be uninstalled before

this installer installs the selected components. (This step requires no user
interaction)
Pre Install Summary step this step gives an overview of the current
selections.
Installing step watch the product features being presented during the
installation progress.
Install Complete step this step is the same as in new installations.
2.1.3 System Manager Installation on Database Server

The System Manager tool is installed together with the NetMaster Server and
provides the NetMaster operators an easier and more flexible way to deal with
some NetMaster administrative tasks:
Set up NetMaster database connection
Upgrade old NetMaster database to a new version
Backup/restore database (requires System Manager on database server)
Schedule database backup and database maintenance tasks
Configure email notification
Start and stop of NetMaster Server
As database backup and restore operations MUST be run on the actual database
server, you have to install System Manager as a standalone application on your
database server if you want System Manager to handle database backup and
restore for you.

A database export will then work like this:

1. User logs on to System Manager on the NetMaster server and requests a
database backup. (Or a periodic database backup job has just started.)
2. A request is sent to System Manager on the database server that runs a
database backup job and stores the export file in the default folder
C:\NgNMS\backup\database on the database server.
3. System Manager on the NetMaster server then copies the newly created
database export file from the database server and places it in the location
specified in the Database view available from the System Manager Settings
menu. The default location is C:\NgNMS\backup\database on the NetMaster
server.
Notes: If System Manager is not installed on the database server, the
database backup and restore feature in System Manager is not
available.
If the local computer has more than one network card, in order
to let know to System Manager which ip can be used for remote
connection with secondary System Manager please define own
ip in C:\Program Files
(x86)\NetMaster\SystemManager\sysman.properties
In the case of a backup done before an upgrade operation
(started either from the Initial Setup Wizard or from the
"Upgrade User/Schema" menu), the backup is kept only on the
database server.
2.1.3.1 Installation
If no existing System Manager installation is detected on the database server, the
installer will run in New Installation mode.
You may cancel the installation at any step until the wizard starts installing the
files.
Press the Install NetMaster button to initiate System Manager installation.
Internet Explorer needs to be told to run the installer:


Internet Explorer needs to know that you trust the installer:

The Installer is preparing to start:

Proceed to install NetMaster by running the Installation wizard as follows:

The Introduction step displays some general information about the installation
process
Click Next to continue the wizard.

Read the license agreement.
If you accept the agreement, select the Accept option and then click Next to
continue.
Choose Install Set step. Select NetMaster Database Server only. This is in fact
System Manager in standalone mode.


Choose Install Folder step.
In this step you can choose where on the file system to install the software.

Choose Shortcut Folder step.

In this step you can choose where to place product icons/shortcuts. Note that
there is an option for creating icons for all Users.

Pre Installation Summary step.

This step gives an overview of the current selections.
Click Install to continue the wizard.

Installing step
Watch the product features being presented during the installation progress.

Install Complete step.

If there were any problems encountered during the installation, see the
installation log file located in the installation destination folder for details.
Click Done to finish the wizard.

2.1.3.2 Configuration
If you open System Manager on the database server the following information is
shown:
All configuration should in general take place using the System Manager that is
installed on the NetMaster server, and not on the Database Server.
However, please note that database backups will by default be saved in a folder on
the same drive as the database installation folder. As the database backups occupy
too large amounts of space on the storage drive, it might be helpful to change the
database folder to a location on a different drive. On a system with standalone
Database Server, this must be done manually.
How to change folder for backups on a standalone Database Server

If you want to change the folder for backups on a standalone Database Server, do
the following:
1. On the database server, go to the folder:
<NetMaster_installation>/SystemManager/conf/system/
2. Open the file:
string@DatabaseBackupPath.xml
3. Change the path to another existing location and save the file
2.1.4 Uninstall NetMaster for Windows

To uninstall NetMaster, run Uninstall NetMaster from the NetMaster program
folder. You can also locate NetMaster in the Add or Remove Programs folder in the
Control Panel and click the Change/Remove button.
Run the Uninstaller wizard:
Click Uninstall to continue the wizard. A confirmation dialog appears:
Click Yes to confirm NetMaster removal.

NetMaster is now uninstalled:
Click Done to exit the NetMaster Uninstaller wizard.

2.2 NetMaster Installation on Solaris
2.2.1 NetMaster Server Pre-installation for Solaris
Register NetMaster Server at DNS

To establish connection between NetMaster Client and NetMaster Server, it is
required that the NetMaster Server host is registered in DNS.
Prepare Database
NetMaster Server requires a database to work. Make sure that a database server is
installed and reachable from the computer on which you want to install NetMaster
Server.
Note: NetMaster supports the Oracle Database Server on the Solaris
platform. For further details, refer to the NetMaster System
Requirements document. We recommend installing a stand-
alone database on Windows Server 2008 64bit platform instead,
using the procedure System Manager Installation on Database
Server.
If the database server is running on a different computer than the NetMaster
Server, the firewall settings on the database server may have to be modified (i.e.
open the port used for communication with the database server).
Oracle database servers are supported, see the NetMaster System Requirements
document for information about supported database editions.
Java installation
The Java Runtime environment (JRE) can be downloaded from the Internet.
Go to the following web page and download version 1.7.0_45:
http://www.oracle.com/technetwork/java/javase/downloads/
After the JRE is installed, do the following steps:
1. Open a command prompt (cmd)
2. Verify that the installed JRE is in PATH by typing java version
3. If the java command is not recognized, you must add the bin directory under
the JRE installation directory to the PATH
If the command is recognized, you shall see the version of the installed JRE
which shall be 1.7_0.45
If the version is not 1.7, do the following (assuming you have version 1.7.0.45):
cd /usr
rm java
ln -s /usr/jre/jre1.7.0_45 java

Prepare Apache Ant

Ensure that Apache Ant of version at least 1.8.1 is installed on the Solaris machine.
If not installed, do the following:
1. Install ant (unpack the archive from folder /ant on installation media) on a file
system with enough space.
2. Create a symbolic link:
ln -s <Ant install folder>/apache-ant-1.8.1/bin/ant /usr/bin/ant
2.2.2 NetMaster Server Installation for Solaris

The following chapter guides you through NetMaster Server, System Manager and
SNMP Agent installation on Solaris platform.
This guide requires that the steps for Pre Installation for Solaris already have been
completed.
NetMaster Server is supported on SUN Solaris 10 operating system and SPARC
platform.
If you want to install NetMaster Client on Solaris 9 platform, use the manual
procedure for NetMaster Client installation for Solaris. Client is also available for
Windows platform, see NetMaster installation for Windows for details.
NetMaster Install Sets

NetMaster allows you to install any of the following install units:
Install Unit Explanation
Server NetMaster Server.
System Manager Configuration and maintenance tool for NetMaster Server. System Manager
must be installed on both the NetMaster Server and the database server.
SNMP Agent Northbound interface to higher-order network management systems
Polyview Topology Enables exporting discovered elements and subnetworks from PolyView
Import into a file and then importing them, while preserving their hierarchy, into
NetMaster as managed elements in administrative domains
All install sets:

Install Set Explanation
Server NetMaster Server, SNMP Agent, System Manager and Polyview Topology
Import
System Manager System Manager only, intended for stand-alone database server installation.
Custom Pick one or more of all available install units

Install Modes
For the Solaris platform, this version of the installer supports only new
installations. (No Upgrade/Maintenance). This means that you must uninstall the
current version before installation.
Please note that the installation of NetMaster on Solaris is less automated
compared to Windows installer, and some steps need to be done manually.
2.2.2.2 New Installation

Note: For the Solaris platform, this version of the installer supports
only new installations, no Upgrade or Maintenance. This means
that you must uninstall the current version before installing a
new version..
Execute the installer as root
Unpack the NetMaster installer netmaster-sol_R****.zip to a temporary folder and
do the following:
cd <temporary folder>/Disk1/InstData/VM/
sh Setup.bin
When choosing installation directory in the installer, ensure that the folder has
enough free space, and is within the boot partition. This is to make sure that the
services will start automatically after a reboot of the machine.
Complete the installation wizard. The steps in the installation for Solaris are
basically the same as in New Installation for Windows, except that Client is not an
option in Solaris version.
If the Installer reports that the installation succeeded with some errors, you can
search for ERROR in <install-dir>/NetMaster_InstallLog.log.
If the only errors relates to Modify Text File and Create Link, then everything is OK.
2.2.2.3 Register NetMaster Services

When installation wizard is completed, register services by executing:
cd <install-dir>
ant
Check Service Status

If you want to check the status of the NetMaster services:
svcs sysman netmaster nifservice
If you installed NetMaster Server (netmaster), System Manager (sysman) and
SNMP Agent (nifservice), the result should be something like this:
STATE STIME FMRI
disabled 10:48:42 svc:/application/netmaster:default

disabled 10:48:44 svc:/application/nifservice:default

online 10:48:51 svc:/application/sysman:default
Start a System Manager Web Browser Session

From a Windows PC, open an Internet Explorer web browser on:
http://<NetMaster server address>:18080/SystemManager/main?dialog=setup
where <NetMaster server address> = address of the server where System Manager
is running.
Proceed with the NetMaster Post installation steps and run the NetMaster Initial
Setup wizard to set up NetMaster Server with a database schema.
2.2.3 Uninstall NetMaster for Solaris

Please note that the uninstallation of NetMaster on Solaris less automated
compared to the Windows version.
Run uninstaller:
sh <install-dir>/Uninstall\ NetMaster/Uninstall_NetMaster
Remove files:
rm -r <install-dir>
rm -r /var/svc/manifest/application/ngnms/

2.3 Post Installation
2.3.1 NetMaster Server post installation

This section describes post installation steps for a NetMaster Server installation.
This guide requires that the steps for NetMaster Installation on Windows or
NetMaster Installation on Solaris already have been completed.
Note that for a new and upgrade installation, NetMaster is not ready to run until
System Manager's NetMaster Initial Setup wizard is completed.
Windows only: Windows Services and Server Monitor

At the end of an installation on Windows platform, the NetMaster Server is
installed as a Windows service and a Server Monitor application is automatically
started (look for the systray icon ). If you don't want the NetMaster Server to
start automatically upon computer reboot, you can set the mode of the NetMaster
Service to manual in the Services applet in the Control Panel.
Windows 2003 only:

In order to manage devices of the IP-20 family, a change in the Windows registry
must be made to avoid running out of sockets.
This change is described in http://support.microsoft.com/kb/196271
2.3.1.2 NetMaster Recommended Settings

The settings are dependent on the network size. The following table presents the
recommneded settings for various sizes:
Network Max Connection Pool Size Max Thread Pool Size Heap Size
size
4000 NEs 500 250 10000
2000 NEs 300 130 5000
1000 NEs 250 100 3000

2.3.1.3 System Manager

The System Manager tool contains database related tasks and also general
NetMaster maintenance tasks intended to ease NetMaster configuration. After
closing the NetMaster Installer you will be prompted to start the System Manager
to complete the NetMaster configuration (this is only valid for Windows platform -
for Solaris platform, System Manager must be launched manually)
Log in using System Manager administrator user. System Manager will if needed
automatically launch the NetMaster Initial Setup wizard that will help you through
the necessary setup pages.
The initial authentication credentials for the System Manager administrator are:
User name: root
Password: pw
Note: It is strongly recommended to change the password of the root
account as soon as possible to prevent unauthorized access. To
change the password, open the System Manager Settings view.
See System Manager online help or PDF document on install media for more
information.
2.3.1.4 NetMaster Heap Size configuration

NetMaster is predefined with a Maximum Heap Size of 768 MB. However this
parameter should be tuned on servers where the number of managed network
elements is expected to increase above 100. The maximum allowed heap size is
highly dependent on available memory on the server.
To configure the heap size:
1. In the NetMaster System Manager: open the Settings menu and click
NetMaster Server.
2. Change the default value for Maximum Heap Size to a new value. i.e. 1400.
3. Restart NetMaster Server
If the server fails to start, reset the Maximum Heap Size, as above, using a
lower value than the one suggested.
If the server starts successfully, leave the server running or increase the
value even further until server start fails. Then use the last value it
successfully started with.
Server should now have an optimal Heap Size.

2.3.1.5 Firewall settings

If connecting any remote NetMaster clients to the server, and the computers
firewall is enabled, it is necessary to configure the firewall to allow the following
ports to be opened towards the NetMaster application server:
Port Description
TCP port 1098 Java RMI Activation Port. TCP port at which the activation system (rmid)
listens
TCP port 1099 Java RMI Registry Port.
TCP port 8089 NetMaster's report feature
TCP port 3873 JBoss EJB 3 socket based invoker layer
TCP port 4446 JBoss EJB3 remote method invocation
TCP port 61616 Used by NetMaster client to connect to an enterprise messaging queue
that runs within NetMaster, used to push events to the client about
changes in services.
In order for NetMaster server to manage network elements, it is necessary to

configure the firewall to allow the following ports to be opened towards the
network elements:
Port Description
TCP port 80 HTTP - Hypertext Transfer Protocol
TCP port 443 HTTPS - Hypertext Transfer Protocol Secure
In order for NetMaster server to act as an FTP server, the following ports must be
opened toward the NetMaster application server:
Port Description
TCP port 20 FTP - File Transfer Protocol [default data]
TCP port 21 FTP - File Transfer Protocol [Control]
In order for NetMaster server to act as an SFTP server, the following ports must be
opened toward the NetMaster application server:
Port Description
TCP port 20 SFTP Secure File Transfer Protocol [default data]
TCP port 22 SFTP Secure File Transfer Protocol [Control]

In order for the NetMaster server to receive traps from network elements, the
following port must be opened:
Port Description
UDP port 162, SNMP trap port.
or any other user Default port is 162, but can be set to a different port in the Snmp
defined port Trap Port Number field in NetMaster Server system manager
view
If the SNMP agent is installed, the following port must be open:

Port Description
UDP port 161 SNMP get/set port
Ports to be opened at the machine where the Database is installed:

Port Description
TCP Port 1521 Oracle Database server
TCP Port 5432 postgres SQL Database server
Ports to be opened at the machine where the System Manager is installed:

Port Description
TCP port 18005 Shutdown port
TCP port 18010 AJP connector port
TCP port 18080 Connector port
TCP port 18443 Redirect port
Ports to be opened at the machine where Northbound SNMP manager is installed:

Port Description
UDP port 162 Northbound SNMP Trap Port
For Windows Firewall, these ports can be opened as follows:

1. Open the Windows Firewall in the Windows Control Panel
2. In the General tab, make sure that On (recommended) is selected and that
Dont allow exceptions is not checked.
3. In the Exceptions tab, click the Add Port. Repeat for all ports to allow.
4. Type the name, i.e. NetMaster JNDI Port.
5. Type the port number, i.e. 1098.
6. Make sure that TCP is selected.

7. If you want to limit the IP addresses that is allowed to connect using this port,
click the Change scope button:
Select Custom list and specify the IP-addresses of all GUI Client computers,
or
Select My network (subnet) only to only allow GUI Clients within your local
subnet.
8. Click OK
9. Click OK
10. In the Advanced tab, make sure that the network connection your computer is
using is enabled (checked) in the Network Connection Settings list.
For other firewalls, different procedures may be required.
2.3.1.6 NetMaster GUI Client

Start the NetMaster Client from the program shortcut folder selected during the
installation process. A Login window will be displayed where the authentication
credentials and the server host name must be entered.
The authentication credentials for the root administrator are:
User name: root
Password: pw
Note: It is strongly recommended to change the password of the root
account immediately after the first login to prevent
unauthorized access. To change the password, open the User
Settings preferences menu.
See the Login dialog section for more information.
The next step is now to discover your network. See the How to discover and
manage an NE section for more information.
2.3.1.7 NetMaster license

In order to run NetMaster, it is necessary to have a license and this can be
activated with a file (sw-nms.key).
If this key file was not available when performing the installation the license can
easily be activated when you receive this from Customer Support. Unzip the .zip
file you received from Customer Support.
Use the System Manager or Server Monitor application to activate the license.
If you do not have a NetMaster license, contact us by making a Technical Support
request or contact your sales representative for an offer.
After the activation of the license, take note that this is only a temporary license
and that it is necessary to make a permanent license.

2.3.1.8 Database administrator user privileges

In order to be able to run the wizards that can be found in the Database Task
view in the NetMaster System Manager on an Oracle database, you need to create
database users with sufficient privileges to perform the tasks:
In order to do initial setup and create and delete user/schema, you need to
have a Database administrator user with similar privileges as a SYSTEM user.
In order to do set active and analyze user/schema, you need to have a
Database administrator user with at least CONNECT, RESOURCE, and SELECT
on SYS.USER$ privileges.
In order to do backup user/schema, you need to have a Database
administrator user with at least CONNECT, RESOURCE, SELECT on SYS.USER$,
SELECT on V_$INSTANCE privileges.
In order to do restore and reinitialize user/schema, you need to have
CONNECT, RESOURCE, SELECT on SYS.USER$, SELECT on V_$INSTANCE ,
SELECT on V_$SESSION, SELECT on V_$TRANSACTION and SELECT on
V_$ROLLNAME privileges.
In order to upgrade user/schema, you need to have a Database administrator
user CONNECT, RESOURCE, SELECT on SYS.USER$, SELECT on V_$SESSION,
SELECT on V_$TRANSACTION and SELECT on V_$ROLLNAME, SELECT on
V_$PARAMETER, SELECT on V_$INSTANCE privileges.
For some Oracle releases, in order to do backup and restore user/schema, the
Database administrator user must have in addition CREATE ANY DIRECTORY
privileges.
2.3.1.9 Maintenance issues

NetMaster Server generates different log files. These files tend to grow large when
managing networks with many elements and heavy traffic.
Delete old server log files

Locate your NetMaster log file directory and remove all files older than three
months:
Installation directory:
<NetMaster installation>\ Server\JBoss-4.2.3\server\ngnms\log
Example for Windows:
C:\Program Files (x86)\NetMaster\Server\JBoss-4.2.3\server\ngnms\log
Backup important files and folders

A full system recovery is likely to take less time if these files and folders are
backed up regularly:
License file for NetMaster:
<NetMaster installation>\Server\JBoss-4.2.3\server\ngnms\license\*.key

Database server connection parameters and other settings (also copy sub
folders):
<NetMaster installation>\SystemManager\conf\*
Database backup files. Can be stored on user configurable folders. Default
folder for Windows is:
C:\NgNMS\backup\database
2.4 Database Installation
2.4.1 NetMaster Database

NetMaster requires an Oracle or PostgreSQL database to be installed and available
for NetMaster use. An installation guide for how to install PostgreSQL on Windows
platform is provided. Please refer to Oracle documentation for instructions how to
install Oracle.
Please note that NetMaster System Manager must be installed on the database
server. Installation of System Manager is only supported for Windows and Solaris
platform. Even though it might be possible to connect NetMaster to a database on
an unsupported platform, some essential features, like backup of database using
NetMaster System Manager, is not supported. We recommend using a system
supporting use of NetMaster System Manager, but if that is not possible, you
should set up backup routines for the database manually.
Database Availability Strategies

Different databases provide different availability strategies for failure and
upgrade. However some considerations are equal and independent of database
solution.
General considerations:
Ensure that the backup is moved to another drive than where the
data/database is located. Ideally it should be copied directly to another
computer.
Always test your strategy. This implies taking a backup and performing a
restore.
What is acceptable down-time if a restore is needed?
What is maximum loss of data accepted if the database server crashes?
Ensure that required configuration and license files are covered by the backup
procedure.
Oracle Backup and Availability Introduction

Oracle provides two different backup strategies that are relevant if you cannot use
NetMaster System Manager:

Export / Import of database: Logical database backup, which includes full

table structure and data. Exports can be run on a nightly basis such that a
possible restore of the database will never lose data older than 24 hours. This
strategy is used by the standard backup/restore in NetMaster System
Manager.
Offline / Cold backups: Database is required to be shut down before taking a
full backup. This allows backup of all data, including log and control files. This
can be achieved by using RMAN.
PostgreSQL Backup and Availability Introduction

PostgreSQL provides three different backup strategies that are relevant if you
cannot use NetMaster System Manager:
Export / Import of database: Logical database backup, which can include full
table structure and data. Exports can be run on a nightly basis such that a
restore of the database will never lose data older than 24 hours. This strategy
is used by the standard backup/restore in NetMaster System Manager.
Offline backup: Database is required to be shut down before taking a full
backup. This allows backup of all data and can be performed by copying the
actual data files.
Online backup: Requires that database is available and running WAL
archiving. With this option one can guarantee 24-hour data recoverability.
Please consult www.postgresql.org if you need more information about how to
install and/or configure PostgreSQL.
2.4.2 Oracle
2.4.2.1 Tips for Working with ORACLE

Important: It is recommended to use fixed IP address on the computer running
Oracle Database Server. If you need to use DHCP, you have to do some additional
pre-installation steps:
If you plan to install Oracle Database Server and NetMaster Server on the same
computer and want to connect from remote NetMaster Clients, you must use
fixed IP address (DHCP will not work)
If you are using a separate computer for Oracle and NetMaster Server, you can
use DHCP on the Oracle computer, but only if you configure a Microsoft
Loopback Adapter on the computer before installing Oracle.
If you plan to install Oracle Database Server, NetMaster Server and NetMaster
Client on the same computer and will not use NetMaster Clients from other
computers, you can use DHCP on the computer, but only if you configure a
Microsoft Loopback Adapter on the computer before installing Oracle.
See section Installing on DHCP computers for more information.

Prevent Oracle password expiry

Please ensure that the Oracle password expiry is set to unlimited.
Installing on DHCP computers

If installing Oracle Database onto a computer that uses the DHCP protocol or a
computer that is not connected to the network at installation time, it is necessary
first to install a loopback adapter and to assign a local IP address to that computer.
Installing a loopback adapter

When installing a loopback adapter, the loopback adapter assigns a local IP for the
computer. After installing a loopback adapter on the computer, there are at least
two network adapters on the computer: the computer's own network adapter and
the loopback adapter. Oracle Database needs to have Windows using the loopback
adapter as the primary adapter.
The primary adapter is determined by the order in which the adapters are
installed : it is the last adapter installed. If installing additional network adapters
after installing the loopback adapter, it is necessary to uninstall the loopback
adapter and reinstall it.
To install the loopback detector:
1. Open the Windows Control Panel.
2. Double-click Add Hardware to start the Add Hardware wizard.
3. In the Welcome window, click Next.
4. In the Is the hardware connected? window, select Yes, I have already
connected the hardware, and click Next.
5. In the If the following hardware is already installed on your computer window,
in the list of installed hardware, select Add a new hardware device, and click
Next.
6. In the wizard can help you install other hardware window, select Install the
hardware that I manually select from a list, and click Next.
7. From the list of hardware types, select the type of hardware you are installing
window, select Network adapters, and click Next.
8. In the Select Network Adapter window, make the following selections:
Manufacturer: Select Microsoft.
Network Adapter: Select Microsoft Loopback Adapter.
Click Next.
9. In the wizard is ready to install your hardware window, click Next.
10. In the Completing the Add Hardware Wizard window, click Finish.
Note: If using Windows 2003, restart the computer now.
11. Right-click My Network Places on the desktop and choose Properties. This
displays the Network Connections Control Panel.

12. Right-click the connection that was just created. This is usually named "Local
Area Connection 2". Choose Properties.
13. On the General tab, select Internet Protocol (TCP/IP), and click Properties.
14. In the Properties dialog box, click Use the following IP address and do the
following:
IP Address: Enter a non-routable IP for the loopback adapter. Oracle
recommends the following non-routable addresses:
192.168.x.x (x is any value between 0 and 255)
10.10.10.10
Subnet mask: Enter 255.255.255.0.
Note: Record the values entered, which will be need later in this
procedure.
Leave all other fields empty.
Click OK.
15. Click OK.
16. Close Network Connections.
17. Restart the computer.
18. Add a line to the SYSTEM_DRIVE:\WINDOWS\system32\drivers\etc\hosts file
with the following format, after the localhost line:
IP_address hostname.domainname hostname where:
IP_address is the non-routable IP address you entered in step 14.
hostname is the name of the computer.
domainname is the name of the domain.
For example: 10.10.10.10 mycomputer.mydomain.com mycomputer

19. Check the network configuration:
Open System in the Control Panel, and select the Computer Name tab. In
Full computer name, make sure the host name and the domain name is
visible, for example, sales.us.mycompany.com.
Click Change. In Computer name, you should see the hostname, and in Full
computer name, you should see the host name and domain name. Using the
previous example, the host name would be sales and the domain would be
us.mycompany.com.
Click More. In Primary DNS suffix of this computer, you should see the
domain name, for example, us.mycompany.com.
Installing on multihomed computers

Oracle Database can be installed on a computer that is associated with multiple IP
addresses (typically achieved by having multiple network cards on the computer).
Each IP address is associated with a host name; additionally, aliases can be set up
for the host name. By default, Oracle Universal Installer uses the
ORACLE_HOSTNAME environment variable setting to find the host name. If
ORACLE_HOSTNAME is not set and you are installing on a computer that has
multiple network cards, Oracle Universal Installer determines the host name by
using the first name in the hosts file, typically located in
SYSTEM_DRIVE:\WINDOWS\system32\drivers\etc on Windows 2003 and
Windows XP, or SYSTEM_DRIVE:\WINNT\system32\drivers\etc on Windows
2000.
Clients must be able to access the computer using this host name, or using aliases
for this host name. To check, ping the host name from the client computers using
the short name (host name only) and the full name (host name and domain name).
Both must work.
Setting the ORACLE_HOSTNAME Environment Variable

To set the ORACLE_HOSTNAME environment variable:
1. Display System in the Windows Control Panel.
2. In the System Properties dialog box, click Advanced.
3. In the Advanced tab, click Environment Variables.
4. In the Environment Variables dialog box, under System Variables, click New.
5. In the New System Variable dialog box, enter the following information:
Variable name: ORACLE_HOSTNAME
Variable value: The host name of the computer that you want to use.
6. Click OK, then in the Environment Variables dialog box, click OK.
7. Click OK in the Environment Variables dialog box, then in the System
Properties dialog box, click OK.
Install NetMaster without Oracle SYSTEM credentials

A new NetMaster installation requires the user to enter database administration
username and password when installing. This procedure may however conflict
with an organizations security policy. In order to overcome this follow the steps
below to avoid using the database administration credentials during the
NetMaster installation.
1. Create the Oracle user manually by following the steps below:
Log into ie. SQLPLUS with SYSTEM privileges. (sqlplus
SYSTEM/password@sid)
Run the sql commands below which will create the NetMaster user:
CREATE USER NetMaster IDENTIFIED BY nmspassword ACCOUNT UNLOCK;
GRANT UNLIMITED TABLESPACE TO NetMaster;
GRANT CONNECT TO NetMaster;
GRANT RESOURCE TO NetMaster;
commit;
2. Start the NetMaster installation.
3. Reinitialize existing (overwrite): The installer will delete the content of the
existing database schema and reinitialize it.
4. Continue the installation.
Oracle Database Version Upgrade

Warning: Ensure that NetMaster Server already has been upgraded to the
newest version before running this procedure. Do NOT attempt to
upgrade both Oracle database version and NetMaster server
version simultaneously, as this may cause an inconsistent
database.
To upgrade the Oracle database version:
1. Use System Manager to perform a backup of the database schemas/users to
keep.
2. Stop NetMaster Server if running
3. Uninstall current version of Oracle by running the Oracle installer and select to
uninstall all components.
Ensure to remove all Oracle application files in the Oracle installation folder.
(Restart of the server could be required for removing all files)
4. Install the new version of Oracle.
5. Use System Manager to perform a restore of the previous database schemas
exported in step 1 in this upgrade guide.
If the "Global Database Name" (SID), "system user name" or "password" was
changed during installation of new Oracle version, ensure to update database
connection parameters in the Restore Wizard step 2/4.
Ensure to use the "Select Database Path" button in the Restore Wizard step 4/4.
This will update the "Database installation path" to the new Oracle version.
6. Use System Manager to remove all scheduled backup tasks.
7. If the Global Database Name (SID), system user name or password was
changed during installation of new Oracle version, then use System Manager
to set the new User/Schema active.
Ensure to use the "Database connection parameters" created in step 5 in this
upgrade guide (the new "Database connection parameters", can now be found by
clicking the "Select Existing Parameters" button in the Set Active User/Schema
wizard).
8. Use System Manager to create new scheduled backup tasks as desired.
Post Installation Settings

1. Run the following commands after installation:
ALTER SYSTEM SET OPEN_CURSORS=3000 SCOPE=MEMORY;
ALTER SYSTEM SET OPTIMIZER_MODE=FIRST_ROWS;
2. Make sure that the database statistics are collected every day

2.4.3 PostgreSQL
2.4.3.1 How to Install PostgreSQL

PostgreSQL is a powerful, open source relational database system. It has more
than 15 years of active development and a proven architecture that has earned it a
strong reputation for reliability, data integrity, and correctness.
NetMaster is compatible with PostgreSQL version 9.1.3. PostgreSQL can be
downloaded free of charge from www.postgresql.org.
The installer walkthrough chapter is an excerpt from
http://www.enterprisedb.com/resources-community/pginst-guide. Please
consult www.postgresql.org if you need more information about how to install
and/or configure PostgreSQL.
Note that you have to perform some post-installation steps to make PostgreSQL
work with NetMaster. Please see the PostgreSQL Post Installation chapter for more
information.
2.4.3.2 Installer walkthrough

The installer (postgresql-9.1.3-1-windows-x64) may be started from an Explorer
window simply by double-clicking it.
The PostgreSQL installer is based on Windows Installer, so it should be familiar to
most Windows users. Following is a quick walkthrough of the installer steps.
1. Introduction screen
Introduction message.

Click Next to get started.

2. Installation Directory
Select the installation directory. You can change the directory by selecting Browse
to pick the new directory.

3. Data Directory
Select the directory under which data will be stored. Note that the 'Data Directory'
option may only be installed on an NTFS partition. If you wish to install the data
directory on any other partition type, you will need to run initdb.exe manually
after installation.

4. Password
Enter and confirm the password to be used for the superuser account (postgres)
in the database cluster. This password is also used for the service account and
must match the current password if the account already exists. You can change the
superuser password independently of the service account password at any time
following the installation.
Note: The Superuser name and password entered in this dialog

must later be used to access the PostgreSQL database when
installing NetMaster and if accessing the database through the
PostgreSQL database administration tool pgAdmin III.
Please note that if a dialog indicating that the "Administrator User Group"
contains "Interactive Users", remove the Interactive user from the Administrators
group and add your user to it instead, as follows:
1. Open the windows user management window: Start | Control Panel | User
Accounts. Select the tab advance and furthermore click on Advanced button in
the middle of the dialog.
2. Select Groups and double-click on the Administrators group on the right side
of the dialog. Remove the NT AUTHORITY\INTERACTIVE user from
Administrators group and add the current user to the same group.
3. Continue the installation with PostgreSQL

5. Port
Select the port that the server will listen on. You may specify a non-default port
number to run the server on (If you change the default port, please make a note of
it, as you will need it while installing the NetMaster server)
If you plan to run NetMaster server and the PostgreSQL server on separate
machines, you will also need to enable access in the host based authentication
configuration (pg_hba.conf) to allow remote users to connect to the server. This is
covered in the chapter on PostgreSQL Post Installation.

6. Advanced Options
Choose the locale that the cluster will be initialized with. By default the locale is
selected as "default locale", from the drop down select "C".
This will initialize the database with ISO C locale and UTF-8 encoding.

7. Ready to install
Click Next to start the actual installation.

8. Installing
A progress bar is shown during the installation.
On some versions of Windows (notably Windows XP before Service Pack 2 and
Windows 2003 before Service Pack 1 - see Microsoft Knowledge Base article
Q818858) a Command Prompt window will appear during the "Initializing
database cluster" step. Don't close this window - it will automatically close once
the operation is complete.

9. Finished
Unselect the option Launch Stack Builder at exit .Installation is complete. You
can now go ahead and test your installation.
Click Finish.

2.4.3.3 PostgreSQL post installation

After installation of PostgreSQL you will have to make some changes in parameter
settings to make it work optimal with NetMaster:
1. Start the pgAdmin tool. You will find it in Start | All programs | PostgreSQL 9.1
| pgAdmin III.
2. Connect to your PostgreSQL database server.
3. Expand the following in the left window: PostgreSQL Database Server ->
Databases -> Postgres.
4. Choose Tools | Server Configuration | postgresql.conf.
5. Locate setting name max_prepared_transactions, double-click on it and change
its value to 150 (or to a value that is equal to or higher than the
max_connections setting listed in Table 1 below). Also select the Enabled
check box.
6. Click OK.

The table below contains required minimum values for running NetMaster with
PostgreSQL:
Parameter name Required Default

max_prepared_transactions 150 100
max_connections 250 100
maintenance_work_mem 32MB 16MB
shared_buffers 64MB 32MB
temp_buffers 16MB 8MB
work_mem 4MB 1MB
checkpoint_segments 12 3
7. In the pgAdmin tool choose File | Save.

8. If you plan to install the NetMaster server on a different server than the
PostgreSQL server, you have to enable access in the host based authentication
configuration.
9. Choose Tools | Server configuration | pg_hba.conf.
10. Add an entry with IP-address and subnet mask of the client that shall be
allowed access to the database server.

More details on this is given in the PostgreSQL online help.

11. In the pgAdmin tool choose File | Save.
12. To make the change take effect the PostgreSQL server will have to reload the
configuration files. From the Windows Start menu choose All Programs |
PostgreSQL 9.1 | Reload Configuration.
13. In the displayed command window, click Return.
NOTE: If the configured changes do not take effect modify the
(Postgres installation dir)/data/pg_hba.conf manually.
2.4.3.4 PostgreSQL database upgrade (version 8.3 - 9.1)

This section describes how to upgrade from previous PostgreSQL versions to
PostgreSQL 9.1.3.
Procedure for migrating to a newer database version

1. Stop NetMaster Server
2. Upgrade NetMaster Server and NetMaster System Manager to latest release
3. Cancel wizard for upgrading database after upgrading NetMaster and System
Manager.
4. Perform a backup of current PostgreSQL database by starting the Backup
Active User/Schema wizard from the Administration | Database Tasks view in
System Manager.
5. Uninstall current version of PostgreSQL. Start ? Control Panel ? Add Remove
Programs. Select PostgreSQL 8.3 and click Remove. Follow the instructions.
6. If the directory C:\Program Files\PostgreSQL\8.3 still exists, it can now be
removed, since it is not in use anymore
7. Install PostgreSQL 9.1. See the Installer walkthrough. Remember to do the post
installation steps for PostgreSQL as described in the PostgreSQL Post
Installation chapter
8. Perform a database restore on the PostgreSQL database by starting the
Restore Active User/Schema wizard from the Administration | Database Tasks
view in System Manager.
NOTE: Use same user/schema parameters as in original database

export and update Database install Path according to new
PostgreSQL installation.
9. Upgrade database by starting the Upgrade User/Schema wizard from the
Administration->Database Tasks view in System Manager.
10. Start NetMaster Server
Postconditional state: NetMaster server should be upgraded to latest release and
running on PostgreSQL 9.1.
PostgreSQL license
PostgreSQL is released under the PostgreSQL License, a liberal Open Source
license, similar to the BSD or MIT licenses.
PostgreSQL Database Management System
(formerly known as Postgres, then as Postgres95)
Portions Copyright (c) 1996-2012, The PostgreSQL Global Development Group
Portions Copyright (c) 1994, The Regents of the University of California
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement is
hereby granted, provided that the above copyright notice and this paragraph and
the following two paragraphs appear in all copies.
IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY
PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS
SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF
CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE
UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE
MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
2.5 High Availability Solution
2.5.1 NetMaster High Availability Solution

The scalable and distributed architecture of NetMaster gives the network
operators great flexibility on how to implement, operate, and manage
communication networks of various types and sizes. As a network grows,
NetMaster can be scaled correspondingly, from a small compact single-server
configuration to a large distributed system.

NetMaster in a small network
NetMaster in a large network
To ensure high availability, two NetMaster NMS systems run in parallel one
Primary system and one Standby system (secondary server). NetMaster high
availability solution replicates the information from the Primary database server
to the Standby database server by running nightly exports of the Primary
database server, and nightly restores on the Standby database server (updating
the Standby database with changes in the Primary database). During the restore
operation, the secondary NetMaster server is automatically stopped to be able to
complete the restore operation. Once the restore operation is completed, the
NetMaster server is automatically restarted and continues to monitor the
network.

NetMaster system with replication
In case of failure, you will need to:

1. Manually log all clients off the Primary NetMaster server and log them into the
Standby NetMaster server.
2. Stop the exports from the Primary database server and the scheduled imports
on the Standby database server.
3. When the Primary server is fixed, create a backup of the Standby database
server and import the data to the Primary database server.
4. Manually log all clients off the Standby NetMaster server and log them into the
Primary NetMaster server.
5. Restart the exports from the Primary database server and the scheduled
imports on the Standby server.
2.5.1.1 High availability solution support

This high availability solution supports the following databases
Oracle 11G R2 SE/EE
PostgreSQL 9.1.3
This high availability solution support the following NetMaster server
configurations
1+1 HA Configuration

2.5.1.2 Terminology and abbreviations

This section describes common terms and abbreviations used throughout this
document.
Batch file / HA Script file: A text file containing a series of commands intended to
be executed by the command interface. Batch files in Windows are postfixed with
.bat or .cmd and can be edited in a simple word editor.
Backup: Refers to making copy of a dataset such that the original dataset can be
restored after a data loss event.
Database: A structured collection of records or data organized by software.
Database administration user: A database user with administrative privileges.
Different databases are likely to have different administrative levels and
associated users.
Database user: A database user which have some given access to the database.
NetMaster Database User: The database user used by NetMaster to create the
content of the schema. This user is typically the owner of all NetMaster related
content and is used for database access by NetMaster server.
Failover: The capability to switch to a redundant system upon a failure.
High Availability (HA): A system design and implementation which together
ensures a certain degree of operational continuity.
Initial Primary server: The server which was initially configured as the Primary
server, regardless of its current role.
Initial Standby server: The server which was initially configured as the Standby
server, regardless of its current role.
Export Database: Copy data out from the database to either a database native
format or a common format.
Import Database: Save data into a database.
NetMaster server: The NetMaster service instance which is monitored by the
NetMaster Server Monitor.
Primary server: The server which is currently in production or in operational
mode.
Restore Database: The process of regaining a previous state.
Standby server: A mirror of a Primary server which is updated to keep data in
synch. This is used for redundancy in a High Availability configuration.
1+1 HA Configuration: A high availability configuration with one Primary server
and one Standby server. NetMaster and the database run on the same server.
2+1 HA Configuration: A high availability configuration with two Primary
servers and one Standby server. NetMaster and the database run separately on
the Primary servers and together on the Standby server.
2+2 HA Configuration: A high availability configuration with two Primary
servers and two Standby servers. NetMaster and the database run separately on

the Primary servers and separately on the Standby server allowing maximum
redundancy and performance.
2.5.2 Installation Instructions

This chapter provides instructions for installing the NetMaster servers and Java
runtime environment, and setting up high availability.
2.5.2.1 Installing NetMaster servers

For both the Primary NetMaster server and Standby NetMaster server complete a
standard NetMaster installation according to the NetMaster Installation Guide.
Note: Ensure that the same user/schema name and user/schema
password are used on both the Primary and Standby servers
when creating a new database user/schema.
Note: If NetMaster System Manager is installed on the database

server, make sure to disable any scheduled backups in order to
avoid duplicate backups and save disk space.
2.5.2.2 Install Java runtime environment (Solaris server only)

See section 2.2.1
2.5.2.3 Manually setting up high availability

This section describes step-by-step how to manually set up the script based high
availability solution.
Note: Ensure that the NetMaster servers and Java runtime
environment were properly installed.
Make high availability scripts available on database servers

The NetMaster high availability solution requires some high availability batch
scripts in addition to the installation performed on the NetMaster and Database
servers. For maintainability and customer support, it is recommended to keep the
high availability batch scripts in a root folder on the database server.
1. On both the Primary and Standby database servers, create the following
folder: C:\NetMaster.
2. Copy the entire batch script folder (named tasks) to the newly created folder
on both database servers: C:\NetMaster\tasks.
Note: If the high availability configuration is a 1+1 setup with one
Primary server and one Standby server, NetMaster and the
database run on the same server.

Start and stop remote NetMaster server

When a restore of the Standby database server is performed, the running Standby
NetMaster server must be stopped and restarted. Service Control (SC) commands
are invoked on the database server to stop services on the NetMaster server.
These commands require sufficient permissions on the NetMaster server.
Note: If the OS user and password is different on the database and
NetMaster server, the SC commands will most likely fail.
To test if you can start and stop a remote NetMaster server:
1. On the Primary database server, open a command and run the following
commands:
sc \\PrimaryNetMasterServerIPstop "ngNMSService"
sc \\PrimaryNetMasterServerIPstart "ngNMSService"
2. On the Standby database system, open command prompt and run the
following commands:
sc \\StandbyNetMasterServerIPstop "ngNMSService"
sc \\StandbyNetMasterServerIPstart "ngNMSService"
Note: If you are not able to stop and start the NetMaster server
remotely, see Enabling remote starting/stopping of NetMaster
server. If the HA Configuration is a 1+1 setup with one Primary
server and one Standby server, NetMaster and the database will
run on same server. To test the start and stop command just run
the PrimaryServerIP and StandbyServerIP commands.
Set-up instructions
1. On both database servers, open the file NetMaster_environment.cmd in a text
editor (e.g., Notepad) and add all required general parameters listed in System
parameter configuration. Make sure that the database parameters are correct
and that the DB_INSTANCE_HOME parameter points to the database home
path.
2. On the Standby database server, create and share the folder: .\tasks\backup\
Give everyone full rights to modify the content (see Sharing folders).
3. On the Primary database server, create and share the folder: .\tasks\backup\
Give everyone full rights to modify the content (see Sharing folders).
4. On the Primary database server, open the file ha_netmaster_environment.cmd
batch script in a text editor (Notepad).
5. Assign the necessary values to the parameters described below (refer to High
availability parameters):
RESTORE_DATABASE_SERVER_UNC_SHARE=<The path to the shared
folder on the (Standby) database server to receive backups after export, ex.
\\StandbyDBserverIP\backup\>

NETMASTER_SERVER_ADDRESS=<The IP address of this (initial Primary)

NetMaster server which should be started and stopped during restore. This
is needed, for example, when a failure has occurred and the initial Primary
server needs to be recovered by restoring the schema using the backup
from the Standby server.>
6. On the Standby database server, open the file ha_netmaster_environment.cmd
batch script in a text editor (Notepad).
7. Referring to High availability parameters, assign the necessary values to the
parameters described below:
RESTORE_DATABASE_SERVER_UNC_SHARE=<The path to the shared
folder on the (Primary) database server to receive backups after export, ex.
\\PrimaryDBserverIP\backup\>
NETMASTER_SERVER_ADDRESS=<The IP address of this (Standby)
NetMaster server which should be started and stopped during restore.>
8. On the Primary (database) server, add the file:
ha_run_netmaster_database_export.cmd to scheduled tasks in Windows.
Schedule the tasks to run every day at 1.00 am. Refer to Creating scheduled
tasks.
9. On the Standby (database) server, add the file:
\tasks\ha_run_netmaster_database_restore.cmd to scheduled tasks in
Windows. Schedule the tasks to run every day at 2.00 am.
Note: We recommend you test the configuration by running it
manually.
To run the tasks manually:
1. On the Primary database server, execute the
ha_run_netmaster_database_export.cmd task (right-click and select Run for
the scheduled service). Note the time it takes for the task to finish (i.e., until
the command window closes). This duration can be used as a guideline as to
when to schedule the subsequent tasks
(ha_run_netmaster_database_restore.cmd). It is important that the restore
operation does not start before the HA export operation is completed.
2. On the Standby database server, execute the
ha_restore_netmaster_database.cmd task (right-click and select Run for the
scheduled service).
3. Check the log files created in the folder ..\tasks\log on both servers. The high
availability export and high availability restore operation is successfully
performed if no error messages are reported.
High availability backup files and filenames

When a high availability database export operation is performed, a new backup is
created on the Primary database server (file size > 0 kb). The file is located in the
folder ..\tasks\backup\ and the filename on the Primary database server is
0_netmaster_database.backup.gz. The previous export file is renamed to
1_netmaster_database.backup.gz. This naming system continues based on the

configuration in the netmaster_environment.cmd file of the number of database

exports to keep.
A database restore candidate is copied to the shared folders on the Standby
database server, ..\\tasks\backup and the filename is
Rnetmaster_database.backup.gz.
The file size and timestamp should be identical to the last export on the Primary
database server. This indicates that the file is not restored but only transferred
from the Primary system.
High availability restore files and filenames

When a high availability database restore operation is performed, the database
restore operation searches for a restore candidate file
(Rnetmaster_database.backup.gz). If found, the restore is performed and once
completed the restore candidate file is flagged and renamed to
0_Rnetmaster_database.backup.gz. As with the backup files, the previous restore
file is renamed to 1_Rnetmaster_database.backup.gz. This naming system
continues based on the configuration in the netmaster_environment.cmd file of
the number of database exports to keep.
2.5.2.4 Configuring Unmodified Trap Forwarding for High Availability

When using the High Availability solution, unmodified trap forwarding must be
manually disabled on the standby server. See Unmodified Trap Forwarding in the
NetMaster User Manual.
2.5.3 Failover Procedure

This chapter provides instructions in case the Primary server fails.
If the Primary server fails, perform the following steps:
1. Manually log all clients onto the Standby NetMaster server.
2. Stop the scheduled database exports on the Primary database server and the
scheduled import on the Standby database. This should be done before the
next restore on the Standby server in order to prevent overwriting the
configuration work performed on the Standby server during Primary server
failure.
3. When the Primary server is fixed and configured as described in the setup
instructions, perform the following:
i. On the Standby (database) server, manually run the following batch script
to create a backup: ha_run_netmaster_database_export.cmd.
ii. On the Primary (database) server, manually run the following batch script
to restore the backup into the Primary server:
ha_run_netmaster_database_restore.cmd.
iii. On the Primary and Standby (database) servers, ensure that nightly
exports and imports are rescheduled according to the instructions in Set-
up instructions.
2.5.4 System Parameter Configuration
2.5.4.1 General database environment parameters

The general database environment parameters are located in the file:
netmaster_environment.cmd.
Parameter name Default value / Comment
<type>
DB_SERVER_ADDRESS <string> IP address or hostname of the database
server. In a 1+1 configuration, the IP address
or hostname of the database server and
NetMaster server is identical.
DB_INSTANCE_NAME <string> Name of the database instance. (Postgres/
NMSORA)
DB_INSTANCE_ HOME <string> The full path to the database installation root
folder.
Example: Oracle 11:
C:\app\Administrator\product\11.1.0\db_1
Example: PostgreSQL 9.1 (required):
C:\Program Files\PostgreSQL\9.1
Note: Use quotes if there is a space in the
path.
DB_NETMASTER_USER <string> Name of the NetMaster user/schema
configured in the installation.
DB_NETMASTER_PASSWORD <string> Password of the NetMaster user/schema
configured in the installation.
DB_ADMIN_USER <string> Default database admin username:
Oracle: SYSTEM (System user name)
PostgreSQL: postgres (Superuser name)
DB_ADMIN_PASSWORD <string> Password of the database system user
configured in the database installation.
DB_ PORT <integer> Default database port:
Oracle: 1521
PostgreSQL: 5432
DB_LOG_PATH .\log Default log path where all logs are written.
DB_ORACLE_SYS_PASSWORD % DB_ADMIN_ (Oracle only) Password to the Oracle SYS
PASSWORD% user. By default this is the same as the ADMIN
(SYSTEM) password.
DB_TYPE <string> Database type definition:
Oracle: ORACLE
PostgreSQL: POSTGRESQL


<type>
DB_VERSION (Oracle only). Possible values are:
1: If the Oracle version is lower or equal
to 11G R1
2: If the Oracle version is greater or
equal to 11G R2
For PostgreSql there is no need to set this
parameter.
2.5.4.2 Database export parameters

The database export parameters are located in the file:
<type>
DB_EXPORTS_TO_KEEP 15 The number of database exports to keep
before wrapping is started and the oldest is
deleted.
DB_EXPORT_FILENAME <string> Name of the database export. The latest
export is prefixed with an export number and
underscore (0_).
Default filename:
Oracle: NetMaster_database.dmp
PostgreSQL:
NetMaster_database.backup
WHERE_TO_KEEP_DB_EXPORTS .\backup\ Path to where the database exports are
stored.
2.5.4.3 Database restore parameters

The database restore parameters are located in the file:
<type>
DB_RESTORE_NUMBER 0 This value defines which database export
number to restore. 0 indicates the latest
export. Larger numbers indicate older
database exports.
DB_RESTORE_TO_INSTANCE_ %DB_INSTANCE_ The database instance to restore the
NAME NAME% database export to.


<type>
DB_RESTORE_TO_USER %DB_ (Oracle only) Defines the user where the
NETMASTER database should be restored.
_USER%
DB_RESTORE_TO_PASSWORD %DB_ (Oracle only) Password for
NETMASTER DB_RESTORE_TO_USER
_PASSWORD%
2.5.4.4 High availability parameters

The high availability parameters are located in the file:
ha_netmaster_environment.cmd.
Parameter name Default Comment
value /
<type>
RESTORE_DATABASE_SERVER_UNC_SHARE <string> Path to share on the other database
server
For example, if this is the Primary
database server, the path should be
pointing to a share on the Standby
database server (the backup will be
copied to the other database server for
restore)
\\ipaddress\backup\
NETMASTER_SERVER_ADDRESS <string> IP address of the NetMaster server
which should be started and stopped
during restore.
For example, if this is the Primary
database server, the IP address should
link to the Primary NetMaster server.
Note: If the high availability
configuration is a 1+1 setup with one
Primary server and one Standby
server, NetMaster and the database
will run on the same server. In this
case, refer to the local server in the
NETMASTER_SERVER_ADDRESS
parameter
2.5.4.5 Script overview and security

The file NetMaster_environment.cmd contains all access parameters to the
NetMaster database server. The file should be located on both database servers in
a high availability configuration.

Note: Consideration must be made whether the security policies of

your organization allow passwords to be stored unencrypted in
text files on the actual server. Bear in mind that it is fairly trivial
for users with file access to the database server to access the
database itself, even if passwords are encrypted.
The table below displays a list of all batch scripts along with the required
privileges and a brief description of the script. If the passwords are omitted, the
batch scripts will not work correctly.
Note: The ADMIN user in this context is the same as:
SYSTEM user in Oracle
Superuser in PostgreSQL
All the batch scripts in this table depend on a properly
configured NetMaster_environment.cmd.
Path Script Command Name Required Required Comment
Oracle DB PostgreSQL
User Rights User Rights
\tasks\ ha_run_netmaster_database_export NMS NMS, ADMIN Exports a given database and
copies a restore file to the
Standby database.
\tasks\ ha_run_netmaster_database_restore NMS, ADMIN NMS, ADMIN Restores a given database if
the restore file is available.
\tasks\ logon_database_as_ADMIN ADMIN ADMIN Forces the native database
sql client to log on to the
database with ADMIN user
privileges.
\tasks\ logon_database_as_NMS NMS NMS Forces the native database
sql client to log on to the
database with NMS user
privileges.
\tasks\ run_environment_report None None Displays the current
environment configuration.
2.5.5 Troubleshooting
This chapter describes common errors and provides instructions to investigate
and resolve the issues. In addition, it provides suggestions as to tools and utilities
that may be useful in tracking down solutions.
2.5.5.1 Tools and utilities

The tasks folder contains several scripts which may help to debug or report the
current preferences.

Report database environment

This script enables you to view the current configuration of the physical server
and all environment parameters. The parameters displayed by this script are also
displayed in other tasks, however, this task does not enable you to perform any
action.
Execute the file: /tasks/run_ environment_report.cmd
Logon database as administrator

This script can be used to verify that the configuration is correct and to execute
administrative commands directly on the database.
Execute the file: /tasks/logon_database_as_ADMIN.cmd
Logon database with NetMaster user

This script can be used to verify that the configuration is correct and to execute
SQL commands directly on the NetMaster database. Note that the scope of this
logon is only within the NetMaster database user/schema and therefore only SQL
commands relevant to the NetMaster database should be executed here.
Execute the file: /tasks/logon_database_as_NMS.cmd
2.5.5.2 Server identity and LAN settings

The following actions should be performed if there are problems with server
identity, IP alias settings or LAN settings.
Computer name
Under My Computer > System Properties > Computer Name > Change, make sure
all servers have the correct names and are configured to belong to the same
Workgroup.
LAN settings
1. Make sure that all required services are activated on both servers.
2. In the Windows Control Panel > Network Connections, right-click and select
Properties for the active LAN connection.
3. Ensure that the following items are enabled:
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
Internet Protocol (TCP/IP)
4. Under Internet Protocol (TCP/IP) > Properties, make sure the IP address
settings are correct.

IP alias setting
Edit the C:\Windows\system32\drivers\etc\hosts file. Add an entry to link the
computer name and IP address of the opposite server,
e.g., 142.22.1.40 Netmaster2.
2.5.5.3 Sharing folders

The following are general guidelines on how to share folders using Windows 2008
Server R2.
1. Right-click the backup folder and select Share with > Specific people.
Share with specific people
2. Select Everyone and click Add.

3. Change the permission level to Read/Write.

Share with everyone
2.5.5.4 Creating scheduled tasks

The following are general guidelines on how to schedule tasks using Windows
2008 Server R2. When scheduling script files to run as scheduled tasks on
Windows 2008 Server R2, it is important to specify start in on the last step.
When scheduling tasks, make sure to select and use an administrator user with
access to the share on the other server.
Note: Do not change the assigned users password, or scheduled tasks
will fail.
1. In the Create a Basic Task Wizard, enter the name and description (optional)
of the task.

Create a basic task
2. Click Next.
Create a basic task task trigger
3. Select when the task should start. (For high availability, it is recommended
that the task run daily.)
4. Click Next.

Create a basic task task trigger daily
5. Enter the start date and time and how often it should run each day.
6. Click Next.
Create a basic task action
7. Select the action to be performed. In this case, select Start a program.

Create a basic task action start a program
8. Browse to and select the program/script to run.

9. In the Start in (optional) field, enter C:\NetMaster\tasks.
10. Click Next.
Create a basic task summary
11. Review the task information and if correct, click Finish.

2.5.5.5 Enabling remote starting/stopping of NetMaster server

If different OS user and password are used to connect to the database server and
NetMaster server in high availability configurations, add the following command
at the command prompt on the database server:
NET USE /PERSISTENT:YES \\NetMasterServerIP\IPC$
/USER:NetMasterServerAdminUser
NetMasterServerAdminUserPassword
Note: In the NET USE command, specify usernames and passwords on
the NetMaster server with sufficient privileges (admin user).
This enables remote connections and provides access to stop and start services on
the NetMaster server remotely from the database server (used during a high
availability restore procedure).
To test remote access:
At a command prompt, run the following commands:
sc \\NetMasterServerIPstop "ngNMSService"
sc \\NetMasterServerIPstart "ngNMSService"
To remove remote access:
At a command prompt, run the following command: net use */delete.
2.5.6 High-Availability Solution for Solaris

This solution is to be used for 2+2 redundancy system, where we have two
subsystems, the active and the standby. Each subsystem consists of a host running
NetMaster server, and another host running the database software.
2.5.6.1 Current Limitations

NetMaster hosts must be running MS Windows
Database hosts must be running Solaris. (Linux is not tested in this version)
Currently, there is no support for 1+1, or 2+1 configurations.
Only the Oracle database is supported.
The system manager on the database machine must be disabled prior to the
upgrade
2.5.6.2 Concepts
Subsystem
A subsystem consists of a host running NetMaster server, and a host running the
database.
Active subsystem
The subsystem that is used for daily tasks. All updates (manage element, define
services, manage users, etc.) shall be done on the active subsystem. It is important
that all NetMaster users are aware of which subsystem is active.
Standby subsystem
The redundant subsystem that is kept synchronized with the active subsystem, on
a scheduled basis, usually daily. This subsystem should be used by NetMaster
clients only for read operations. Please note: There is nothing that prevents users
from updating the standby subsystem, but these updates will be lost upon
synchronization.
Synchronization
The process of backing up the active system, transferring the backup to the
standby system, and then restoring the standby system.
2.5.6.3 Functionality
The ha main script

The ha-main script is run on each db server. It performs actions according to the
following logic:
Check if I have connection to the other part,
If YES:
Check my role
If ACTIVE:
Make a backup
Rename local backup files, such that 0_* becomes 1_*, and oldest is deleted if
the maximum number of saved backups has been reached
Transfer the backup to the standby subsystem
Start restore on the standby subsystem
If STANDBY:
Nothing more to do, exit script.
If NO (The system is in isolated mode):
Make a backup (I cannot know if the other system has crashed, the best thing
to do is backup what I have)
Rename local backup files
The ha restore script

When the active server starts a restore on the standby subsystem, the standby
host will do the following:
1. Stop the NetMaster server
2. Rename local backup files
3. Restore the database with the latest backup
4. Start NetMaster server
The log will show what decisions/actions were taken, and report on lost contact,
or other errors.
How roles are determined

Determination of which server is active and which is standby is based on the file
active-ip.
The rules are as follows:
db1.active-ip is missing, db2.active-ip is missing : ha1 is active
db1.active-ip is missing : content of db2.active-ip determines which subsystem
is active
db2.active-ip is missing : content of db1.active-ip determines which subsystem
is active
Content of active-ip is same : content of active-ip determines which subsystem
is active
Content of active-ip differs : ha1 is active
Content of active-ip is neither ip of db1 nor db2 : ha1 is active
When the roles are determined by these rules, the file active-ip is updated on db1
and db2, as necessary.
2.5.6.4 Installation Guide
Terminology
The hosts are referred to as follows:
nm1 - 1. NetMaster host
nm2 - 2. NetMaster host
db1 - 1. database host
db2 - 2. database host
The subsystems are referred to as follows:
HA1 - nm1 + db1 subsystem
HA2 - nm2 + db2 subsystem
Prerequisites
Identical version of the Oracle database installed on db1 and db2.
NetMaster server installed on nm1 and nm2.
nm1 connected with database schema on db1
nm2 connected with database schema on db2
Both use same database schema name and password.
The following software installed on both db servers
Samba (see appendix: Problems & Solutions if Samba net not found)
An ssl/ssh implementation (see appendix: install ssl/ssh)

Main Installation Stages

The main installation stages are:
On the two database hosts, create an HA user
Set up ssh keys such that the HA users can perform ssh/scp actions without
passwords.
Unpack the nms-ha.zip file on HA home directory on HA1
Configure the ha-env.sh script
Configure the ha-cronjob.sh script
Transfer scripts to HA2
Configure the IP address
Set tnsnames.ora
Check NetMaster stop/start
Give permissions
Schedule daily run of ha-main.sh on each machine
The detailed steps for each stage follow below.
Tip: If you login as root, and then must switch user to ha, type su -
ha (notice the hyphen). You are thereby transferred to the
home directory of the user ha.
Create an HA user
User : root
On both hosts db1 and db2, create an HA user, as shown in the following example.
Example:
useradd -d /export/ha -m ha
passwd ha
Note: The user name can be chosen freely in the following pages, ha
is used).
Setup ssh keys

1. On both db1 and db2 hosts:
2. Log in as ha.
3. Run ssh-keygen -t rsa
4. Click Enter in response to questions.
5. After ha user is created on both db1 and db2, do the following:
On db1:
scp .ssh/id_rsa.pub <db2-ip>:.ssh/authorized_keys
(Type "yes" in response to the question are you sure you want to ..., and
provide the password to ha on db2)

On db2:
scp .ssh/id_rsa.pub <db1-ip>:.ssh/authorized_keys
(Type "yes" in response to the question, are you sure you want to ..., and
provide the password to ha on db1)
6. Check that ssh is set up correctly:
On db1, type: ssh <db2-ip>. If the system responds with a remote
session on db2, requiring a password, this is an indication that ssh is set up
correctly.
Perform the same check on db2: ssh <db1-ip>
Unpack ha.zip
1. On db1 host, copy the file ha.zip to a folder accessible by the ha user.
2. Log in to db1 as ha.
3. Unzip ha.zip to the home folder.
4. Check that folder netmaster-ha is created.
Type the following:
chmod +x netmaster-ha/*.sh
chmod +x netmaster-ha/bin/*.sh
Configure ha environment
User : ha
1. If ha-env.sh does not exist already, copy ha-env-example.sh by typing the
following:
cp ha-env-example.sh ha-env.sh
2. Edit the ha-env.sh file.
see Configuration Files
Configure ha-cronjob.sh
User : ha
The file ha-cronjob.sh contains scheduling data for recurrent running of ha-
main.sh script.
By default, ha-cronjob.sh schedules ha-main.sh to run every night at 1:00
A.M. :
####################################
#Script for scheduling ha-main.sh
####################################
00 01 * * * * /export/ha/netmaster-ha/ha-main.sh

To reschedule so that ha-main.sh runs every half-hour, for example, edit the file
as follows:
00,30 * * * * * /export/ha/netmaster-ha/ha-main.sh
Edit to reflect your needs.
Note: Ensure that the path to ha-main.sh is absolute (i.e., begins
with a backslash character - "/")
See also man crontab
Transfer scripts
User : ha
When you have set up the ha-env.sh and ha-cronjob.sh with the correct
values for your system, the next step is to transfer the scripts to the other ha part.
On host db1, as user ha, execute the commands:
cd ~
scp -r netmaster-ha <ha2-ip>:.
Warning! All files under netmaster-ha will be transferred to ha2. If you
have backups they will also be transferred. If you need to
transfer only specific files, see man scp
Configure the IP address

User : ha
Hosts : db1 and db2
If the host has several network adapters, the ip address to be used for
communication with the other HA host should be explicitly specified.
To determine whether its necessary to specify the host ip address, do the
following:
1. On db1 and db2 hosts, log in as ha.
2. Execute the following command (on one line):
echo `/usr/sbin/ifconfig -a | grep inet | grep -v '127.0.0.1' | awk '{ print $2}'`
If the result is a single line of output resembling the line immediately
below, the ip addresses are correctly specified and no additional steps are
necessary.
192.168.56.101
If the result is more than one line of output, resembling the lines
immediately below, proceed with the steps below.
12.66.32.151
12.66.102.1
12.66.102.7
0.0.0.0

3. Determine which ip address is reached, when connecting from the other end
by executing the following command from the other end: ping <ip-
address>
4. Create file netmaster-ha/my-ip with the ip-address as content. This ip
address should be the one specified in the ha-env.sh file under
HA?_DB_SERVER_ADDRESS. The following is an example of creating the my-ip
file:
echo 12.66.32.151 > my-ip
Give permissions
In order to allow user oracle to write backups and log files to ha users
netmaster-ha/exports directory, and to allow user ha to run export/import,
do the following on both db host machines:
1. While logged in as root user, type usermod -G oinstall ha
2. Logout user ha and login as user ha again (this is to let usermod take effect).
3. While logged in as user ha, type:
chgrp oinstall exports/
chmod g+w exports/
Set tnsnames.ora
While logged in as user root, ensure that the file tnsnames.ora exists in
directory ${ORACLE_HOME}/network/admin
It should contain (as a minimum) the following:
<SID> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = <ip-address>)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = <SID>)
)
)

Sample content of tnsnames.ora
NMSORCL4 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.24.90.4)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = nmsorcl4)
)
)
Ensure that the tnsnames.ora file is owned by user oracle, and has oinstall
group.
Check NetMaster stop/start

User : ha
On db1 host, while logged in as user ha, type the following command on one line:
net rpc service status ngNMSService -I <nm1-ip> -U
<HA1_NM_SERVER_ADM_USER>%<HA1_NM_SERVER_ADM_PASSWORD>
The result should be similar to the following:
NetMaster service is running.
Configuration details:
Controls Accepted = 0x45
Service Type = 0x10
Start Type = 0x2
Error Control = 0x1
Tag ID = 0x0
Executable Path = C:\NetMaster\Server\JBoss-4.2.3\bin\wrapper.exe
-s C:\NetMaster\Server\JBoss-4.2.3\conf\wrapper.conf
Load Order Group =
Dependencies = /
Start Name = LocalSystem
Display Name = NetMaster Server
If the system returns the following, see Appendix: Problems & Solutions,
Cannot find samba net program to fix the problem.
net: command not found

If the system returns the following, correct the admin user and password:
Could not connect to server 137.133.9.28

The username or password was not correct.
Connection failed: NT_STATUS_LOGON_FAILURE
If system returns the following, start the netlogon service on the nm host.
Could not connect to server 137.133.9.24

Connection failed: NT_STATUS_NETLOGON_NOT_STARTED
Schedule daily runs

The ha-main.sh script should be scheduled to run recurrently on both db1 and
db2 hosts.
To set up ha-cronjob.sh, type crontab ha-cronjob.sh
To see what is currently scheduled, type crontab -l
To remove currently scheduled job, type crontab -r
Crontab Restrictions
You can execute crontab if:
Your name appears in the file /usr/lib/cron/cron.allow.
Your name does not appear in the file /usr/lib/cron/cron.deny.
Note that:
If only cron.deny exists and is empty, all users can use crontab.
If neither file exists, only the root user can use crontab.
The allow/deny files consist of one user name per line.
See also http://www.adminschoice.com/crontab-quick-reference/
Unmodified Trap Forwarding

When using the High Availability solution, unmodified trap forwarding must be
manually disabled on the standby server. See Unmodified Trap Forwarding in the
NetMaster User Manual.
2.5.6.5 Configuration Files

This chapter covers the content of the files
ha-env.sh
bin/strings.sh
my-ip

ha-env.sh
The following table describes all properties that need to be set in ha-env.sh file.
Many names in this file will have two similar entries, one for HA1 and one for HA2.
Such properties will be mentioned once in the table with HA? prefix.
Tip: In case HA1 and HA2 use same value for a property, that can be
set as follows (note the $):
HA1_DB_PORT=1521
HA2_DB_PORT=$HA1_DB_PORT
Name Example value Description

HA?_NM_SERVER_ADDRESS 137.133.9.28 The ip address of NetMaster servers
HA1_NM_SERVER_OS windows The os of the host running NetMaster server.
HA?_NM_SERVER_ADM_USER administrator Name of an administrator user that is allowed to
login to the NetMaster host
HA?_NM_SERVER_ADM_PASSWORD pw123 Password of the administrator user
HA?_DB_SERVER_ADDRESS 192.168.56.103 The ip address of the database servers
HA?_DB_NAME orcl The db instance name (SID). For oracle these
values will be used to set ORACLE_SID on db1
and db2 hosts.
HA?_DB_HOME /oracle/... The db home dir. For oracle this value will be used
to set ORACLE_HOME on db1 and db2 hosts.
DB_NM_USER netmaster The database schema user for the NetMaster
application.
DB_NM_PASSWORD nm123 The database schema password for the
NetMaster application.
HA?_DB_ADMIN_USER system Name of a db admin user
HA?_DB_ADMIN_PASSWORD adminpw Password of the db admin user
HA?_DB_PORT 1521 The ports used for connection to the db
HA?_LOG_DIR ~/netmaster-ha/log The dir used to store the HA logs.
DB_TYPE oracle Type of the database.
DB_VERSION 1 If db type is oracle, version is set to 1 for oracle
version less than 11.2, and 2 for oracle version
11.2 and up
DB_EXPORTS_NUM 5 Number of exports to keep
DB_EXPORTS_DIR ~/netmaster- Base dir for exports. local exports will be kept
ha/exports here. Remote exports will be kept in subdir
remote

Name Example value Description

debug false Allowed values: false or true.
Controls the amount of logging. If set to true, the
log will be more wordy, logging information used
for debug.
strings.sh
The strings.sh file may need to be modified if the language used in the Solaris
environment is other than English.
The default content of this file is as follows:
#!/bin/bash
# strings may need to be changed, based on language.

#
# The reason for using error codes instead of return
values, is that on solaris, scp returns 1, regardless of
error type
#
# The following strings may be contained in stderr when

running scp, in case of an error condition.
NO_SUCH_FILE="No such file"
TIME_OUT="timed out"
# The following strings are used to determine NetMaster

service state.
# If first line of stdout when run net rpc service status
... contains one of the following strings,
# that is used to determine service state.
SERVICE_STOPPED="stopped"
SERVICE_STOP_PENDING="stop pending"
SERVICE_RUNNING="running"
my-ip
The my-ip file may be needed in case a db host has multiple ip addresses. See
Configure the IP address.

2.5.6.6 User Manual
Check time of last run

To check the time of the last run, execute:
ls -l log/
Example run:
ls -l log/
total 39178
-rw-r--r-- 1 ha other 115618
May 6 18:09 ha-stb.log
-rw-r--r-- 1 ha other 19879232 May
15 12:42 ha.log
The results list shows the timestamp of last modification to the logs. If you want to
check the time of the last run on the other ha end, do a remote login (see remote
login) and execute the above command.
Check status of the HA system

You can check the HA system status to see
Which server is active and which is standby
Do the systems have connectivity?
To check the HA system status, run the command:
./ha-status.sh
Example run:
-bash-3.2$ ./ha-status.sh
Active : HA1 (137.133.9.70)
Standby : HA2 (137.133.9.79)
This host : HA1 (137.133.9.70)
If ha1 and ha2 have connectivity, you dont need to run this command on both
systems. Run it on either db1 or db2 host - the result should be the same.
Restore a selected backup.

User : ha
Backups are stored in the following directories:
Local backups - ./netmaster-ha/exports
Remote backups - ./netmaster-ha/exports/remote
Backups are named <N>_NetMaster_database.dmp.gz, where <N> is 0 for

the last backup.
To see the time of the backup files, execute:
ls -l exports/
To restore the latest backup taken from the remote end, execute:
./ha-restore.sh
To restore a specific backup taken from the remote end, execute:
./ha-restore.sh <N>
or
./ha-restore.sh <N> remote
To restore a specific backup taken from the local end, execute:
./ha-restore.sh <N> local
Running ha-restore will do the following:
Stop NetMaster service if it is running
Restore the database
Start NetMaster service
The restore is executed for ha1 if run on db1, and for ha2 if run on db2
Create a backup
User : ha
To create a backup, log in as user ha to the db host you want to backup and
execute:
bin/ha-backup.sh
To back up the active system, and restore it on the standby system, run from
the active db host:
./ha-main.sh
Switch server roles

User : ha
To switch server roles, such that the active part becomes standby, and vice
versa, execute:
./ha-set-active [ HA1 | HA2 ]
Note: If ha1 and ha2 have connectivity, you dont need to run this
command on both systems. Run it on either the db1 or the db2
host - the result should be the same.
Check logs
User : ha
Log files are located at netmaster-ha/log
Remote login to the other ha end

User : ha
To log in remotely to the other ha end, execute:
ssh <ipaddress of other db? host>
2.5.6.7 Use Cases

This chapter presents commonly use cases encountered in the day to day
maintenance of NetMaster HA system.
Use case : The standby NetMaster host or db host crashes

Actions:
Fix or replace the broken host, re-install and re-configure software.
Implications:
No downtime, as active part is functioning.
Use case : The active NetMaster host crashes

Actions:
1. If many configuration changes have been performed in the time period
between the last synchronization and the crash, run ha-main.sh on active
db host. This step can be skipped, if desired.
2. Perform a switchover.
3. Inform NetMaster users to logon to the now active NetMaster server
Fix or replace the broken host, re-install and re-configure software.
Implications:
Downtime from the time of the crash until users are informed to use other
host.
Changes on active system, made after the last synchronization, will be lost,
unless you perform a manual synchronization (step 1 above).
Note: It is important to perform the switchover as soon as possible
otherwise, the now dead active db will be synchronized with
the standby db. It is better to not perform a switchover back to a
previous active db, because any switchover potentially loses
some of the most recent changes.
Use case : The active db host crashes.

Actions :
1. Perform a switchover.
2. Inform NetMaster users to logon to the other NetMaster server
3. Fix or replace the broken host, re-install and re-configure software.

Implications:
Downtime from the time of the crash event until users are informed to use
other host.
Changes on active system, made after last synchronization, will be lost.
Note: It is better to not perform a switchover back to a previous active
db, because any switchover potentially loses some of the most
recent changes.
Use case : Connectivity between db1 and db2 hosts is lost

Actions:
Fix connectivity
Implications:
Standby system will not be synchronized until connectivity is restored.
2.5.6.8 Appendix I: Install SSL/SSH
How to check if ssl/ssh is installed

User : root
On a command line, run the following commands:
which ssh
which scp
If ssl/ssh is installed, the result should resemble the following:
ha2 $ which scp
/usr/bin/scp
ha2 $ which ssh
/usr/bin/ssh
If ssl/ssh is not installed, the result should resemble the following:
no ssh in /usr/bin /bin
How to determine the processor architecture

To determine processor architecture, run the following command:
mach
The result will be one of the following:
i386
sparc

Downloading OpenSSL/OpenSSH
In case there is no ssl/ssh implementation installed on the Solaris host, it can be
downloaded using the following links:
For SPARC architecture:
http://artfiles.org/sunfreeware.com/pub/freeware/sparc/10/
For i386 architecture:
http://artfiles.org/sunfreeware.com/pub/freeware/i386/10/
The required packages are:
OpenSSL
ZLib
GNU Compiler Collection
OpenSSH
Select the latest stable versions, download them and place them on a disk
accessible from the Solaris host.
Installing OpenSSL/OpenSSH
User : root
Unzip and install gcc
solaris10# gunzip libgcc-3.4.6-sol9-sparc-local.gz
solaris10# pkgadd -d libgcc-3.4.6-sol9-sparc-local
You should receive the following message:
Installation of <SMCgcc> was successful.
Unzip and install zlib
solaris10# gunzip zlib-1.2.1-sol9-sparc-local.gz
solaris10# pkgadd -d zlib-1.2.1-sol9-sparc-local
Installation of <SMCzlib> was successful.
Unzip and install OpenSSL
solaris10# gunzip openssl-0.9.8f-sol9-sparc-local.gz
solaris10# pkgadd -d openssl-0.9.8f-sol9-sparc-local
Installation of <SMCossl> was successful.
Unzip and install OpenSSH
solaris10# gunzip openssh-4.7p1-sol9-sparc-local.gz
solaris10# pkgadd -d openssh-4.7p1-sol9-sparc-local

The packages are now installed.

Run the following script while logged in as user root:
#!/bin/sh
# Create sshd startup/shutdown script

cat << 'SSHD' > /etc/init.d/sshd
#!/bin/sh
case "$1" in
'start')
/usr/local/sbin/sshd
;;
'stop')
/usr/bin/kill `/usr/bin/head -1 /var/run/sshd.pid`
;;
'reload')
/usr/bin/kill -HUP `/usr/bin/head -1
/var/run/sshd.pid`
;;
*)
echo "Usage: $0 { start | stop }"
exit 1
;;
esac
exit 0
SSHD
chown root:root /etc/init.d/sshd
chmod 555 /etc/init.d/sshd
ln -s /etc/init.d/sshd /etc/rc2.d/S98sshd
# Create ssh keys

/usr/local/bin/ssh-keygen -t rsa1 -f
/usr/local/etc/ssh_host_key -N ""
/usr/local/bin/ssh-keygen -t dsa -f
/usr/local/etc/ssh_host_dsa_key -N ""

/usr/local/bin/ssh-keygen -t rsa -
f /usr/local/etc/ssh_host_rsa_key -N ""
/usr/local/bin/ssh-keygen -t ecdsa -f
/usr/local/etc/ssh_host_ecdsa_key -N ""
# Use only ssh protocol 2

sed -e 's/#Protocol 2,1/Protocol 2/'
/usr/local/etc/sshd_config >
/usr/local/etc/sshd_config_new
mv /usr/local/etc/sshd_config_new
/usr/local/etc/sshd_config
# Create privilege separation user and environment

mkdir -m 755 /var/empty
chown root:root /var/empty
groupadd sshd
useradd -g sshd -c "OpenSSH privilege separation user" -d
/var/empty -s /bin/false sshd
# start sshd
/etc/init.d/sshd start
2.5.6.9 Appendix II: Log File Rotation

Solaris is shipped with the logadm tool. This can be used to rotate the ha and
oracle log files.
It can be set up to rename logs in the following situations:
When they reach a certain size
When they reach a certain age
See the following resources:
http://docs.oracle.com/cd/E19963-01/html/821-1462/logadm-1m.html
http://www.softpanorama.org/Logs/Log_rotation/log_rotation_in_solaris.shtml
http://www.c0t0d0s0.org/archives/6394-Less-known-Solaris-features-logadm.html
2.5.6.10 Appendix III: Problems and Solutions
Appendix III: Problems & Solutions

Problem: Export fails with error code: ORA-12154
Solution: You must define tnsnames.ora properly.
Problem: Cannot find samba net program

The command which net returns:
no net in /usr/sbin /usr/bin ...
Solution:
1. Check if samba is installed:
bash
for i in SUNWsmbac SUNWsmbar SUNWsmbau SUNWsfman
> do
> pkginfo $i
> done
If the response is a list resembling the following, then samba is installed:

system SUNWsmbac samba - A Windows SMB/CIFS fileserver for UNIX
(client)
system SUNWsmbar samba - A Windows SMB/CIFS fileserver for UNIX
(Root)
system SUNWsmbau samba - A Windows SMB/CIFS fileserver for UNIX
(Usr)
system SUNWsfman GNU and open source man pages
2. Search for the net program as follows:

find / -name net -print |grep sfw
3. When found, put the path into the ha-env.sh file:
...
NET=/usr/sfw/bin/net
#or:
#NET=/usr/sfw/sbin/net
Problem: When running the net program, the output starts with message similar
to this:
[2013/05/15 10:15:28, 0] param/params.c:(536)
params.c:OpenConfFile() - Unable to open configuration file
"/etc/sfw/smb.conf":
No such file or directory
Solution:
User : root
Check for the existence of the file /etc/sfw/smb.conf on db1 and db2 hosts.

If the file doesnt exist, then execute the following command while logged in as
root::
cp /etc/sfw/smb.conf-example /etc/sfw/smb.conf
Problem:
Restore fails. log/ha-stb.log shows
ORA-01940 cannot drop a user that is currently connected
Solution:
This error occurs when a NetMaster user is currently logged in to the database.
That may happen because the NetMaster server has not been stopped, or because
there is another session (typically sqlplus interactive session) active.
Ensure that ha-env.sh is setup correctly, such that the ha-restore.sh script
succeeds in stopping the NetMaster server before proceeding to perform the
database restore. Ensure also that interactive sessions are closed.
Problem:
When running ./ha-status.sh, the output reports multiple ip addresses, as
follows:
Disagreement on who is active system:
HA2 (20.66.53.51
20.86.10.1
20.86.10.2
Solution:
See Configure the IP address.
Problem:
When running restore the log shows ./ha-status.sh, the output reports multiple
ip addresses as follows:
...
===============================================================
=
Restore script start at : Mon Jun 17 16:13:51 EDT 2013
===============================================================
=
mv /db_restore/HA/netmaster-
ha/exports/remote/0_NetMaster_database.dmp.gz /db_restore/HA/netmaster-
ha/exports/remote/1_NetMaster_database.dmp.gz
actual-status stopped
Control service request failed. [DOS code 0x00000426]
actual-status stopped

ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[/<password>][@<connect_identifier>] | /
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[/<password>][@<connect_identifier>] | /
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
Import: Release 10.2.0.4.0 - Production on Mon Jun 17 16:14:01 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
Production
Export file created by EXPORT:V10.02.01 via conventional path
import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses WE8ISO8859P1 character set (possible charset conversion)
. importing NETMASTER1's objects into NETMASTER1
. . importing table "AXXRPC_USER" 0 rows imported
. . importing table "CORE_DISCOVER_SETTINGS" 5 rows imported
. . importing table "CORE_EJB3_SEQUENCE"
IMP-00019: row rejected due to ORACLE error 1
IMP-00003: ORACLE error 1 encountered
ORA-00001: unique constraint (NETMASTER1.PK_CORE_EJB3_SEQUENCE)
violated
...
Solution:
The error messages for IMP-00019,IMP-00003,and ORA-00001 are a result
incorrect connection parameters for running sqlplus under admin. This is
indicated by the messages for SP2-0306 and SP2-0157 above.
To resolve the problem:
1. Check values in ha-env.sh for:
HA1_DB_ADMIN_USER
HA1_DB_ADMIN_PASSWORD
HA2_DB_ADMIN_USER
HA2_DB_ADMIN_PASSWORD
2. Ensure that values are correct by starting an sqlplus session (execute the
following command):
$DB_HOME/bin/sqlplus -s
<DB_ADMIN_USER>/<DB_ADMIN_PASSWORD>@<MYIP>:1521/<SID>

2.6 External Documents
2.6.1 System Requirements

System requirements for NetMaster are described in the document NetMaster
System Requirements.pdf.
2.6.2 Technical Description

For information about NetMaster architecture, see the document NetMaster
Technical Description.pdf.

3. Migration from PolyView to NetMaster
3.1 Overview
For PolyView NMS customers that are migrating to the NetMaster NMS, a special
tool is provided to import:
The managed elements from PolyView into NetMaster (see Importing
Topology from PolyView to NetMaster).
NetMaster processes the list of elements that were managed by PolyView
and carries out the discovery and manage processes on these elements.
The elements are placed in the Geographical or Logical Trees under the
same hierarchy that existed in PolyView.
The PolyView users (not Groups) into the NetMaster (see Importing users
from PolyView to NetMaster).
The users to be imported into NetMaster are selected from the list of users
that were defined in PolyView.
3.2 Importing Topology from PolyView to NetMaster

You can export discovered elements and subnetworks from PolyView into a file
and then import them, while preserving their hierarchy, into NetMaster as
managed elements in administrative domains. This can spare you the need to
enter all the IP addresses again and create the domain hierarchy manually.
Note: NetMaster supports only IPv4 addresses. Import will not

succeed if the network elements in PolyView only have IPv6
addresses.
3.2.1 Step 1: Create a PolyView Export File

1. In the PolyView topology tree, select which part of the network data to export.
2. Select File > Export data. The Export Data window appears.

3. In the Data types area, clear the checkboxes of any data types you wish to
exclude from export.
4. In the File area, enter or browse to the desired output destination path and
filename.
5. Click OK to perform the export.
3.2.2 Step 2: Prepare for Import into NetMaster

Before starting the import process, you may want to prepare in any of the
following ways:
The topology import process is guided by NetMasters default connection

templates. To enable the process to discover elements with a custom community
name, change the default connection template accordingly.
By default, the import process places elements in the geographical map. However,
you can instruct the import process to place the element in the logical map by
changing the defaultDomain parameter in the config.properties file, from:
defaultDomain = G
to
defaultDomain = L
By default, the import process performs all import stages: parsing the import file,
discovering elements, creating an administrative domains (AD) tree, and
managing the elements. However , you can instruct the import process to
perform only some of these stages by setting the processMode parameter of the
config.properties file to any of the following values:
0 only parse the import file and display a summary
1 parse and discover
2 parse, discover, and create an AD Tree
3 parse, discover, create an AD Tree, and manage. This is the default

setting.
Note: The config.properties file is located in the NetMaster

installation folder, under
.../NetMaster/PolyTopoImport/conf.
3.2.3 Step 3: Run the Topology Import Tool

Note: The topology import tool is located in the NetMaster installation
folder, under .../NetMaster/PolyTopoImport.

1. Make sure the NetMaster server is running.

2. Make sure no other discovery or management process is running.
3. Make sure you have PolyTopoImport permission. Note that all Administrators
group members have this permission.
4. On the computer running the NetMaster server, run the command line tool as
follows:
In Windows, run:
polytopoimporter.bat <filename.exp>
or
polytopoimporter.bat <filename.exp>
<subdomain1/subdomain2/subdomain3/>
In Unix, run:
polytopoimporter.sh <filename.exp>
or
polytopoimporter.sh <filename.exp>
<subdomain1/subdomain2/subdomain3/>
where:
<filename.exp> is the full path and name of the export file. For
example:
c:\67-68.exp.
<subdomain1/subdomain2/subdomain3/> instructs the tool to place

all hierarchical domains exported from PolyView under:
Geographical/subdomain1/subdomain2/subdomain3
or
Logical/subdomain1/subdomain2/subdomain3
3.2.4 Step 4: View Import Results

After import is complete, you can view a summary of the parsing, discovery and
management operations in the console and the log file. The summary lists, for
example:
How many IPs were successfully discovered and managed during the import
process.
The elements that failed to be managed, together with the reason for failure. You
can also view these elements in the Unmanaged Elements view.
The error titles of any errors that occurred. For detailed error information, see
the error log.

Note that if the import file contains IPs that are already managed in NetMaster,
these IPs are not affected by the import process. These IPs will be reported in the
console and the log file.
3.3 Importing users from PolyView to NetMaster

Only the root user is allowed to import PolyView users. Only PolyView users can
be imported, not PolyView groups. After they are imported, users are assigned to
the default group and may be reassigned to other groups. If an imported PolyView
user already exists in NetMaster, the existing user's attributes are overwritten by
the imported user.
Note: An Admin user cannot be imported from PolyView.
3.3.1 Step 1: Export PolyView User Definitions to a File

1. Select Start > All Programs > PolyView > PolyView Server Security or in
CeraMap, select Settings > Security Settings to open the PolyView server
security application.
2. Select File > Export users to save user definitions to a file.
3.3.2 Step 2: Import the User Definitions into NetMaster

The views needed here are found in the User Management perspective.
1. In the User Administration view select the Import PolyView Users operation.
An Open window appears, allowing you to select the import file.
2. Navigate to and select the file created in Step 1 above, and click Open. An
Import users window opens.

3. Select the users to be imported and click OK. The new users will appear in the
Users table.
4. Select the new user in the Users table and then select an appropriate group in
the Groups table.

NetMaster Installation Guide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

NetMaster Installation Guide

Enviado por

Direitos autorais:

Formatos disponíveis

NetMaster NMS

Copyright 2015 by Ceragon Networks Ltd. All rights reserved.

Open Source Statement

Ceragon Proprietary and Confidential Page 2 of 105

3. Migration from PolyView to NetMaster ........................................................ 101

Ceragon Proprietary and Confidential Page 3 of 105

Ceragon Proprietary and Confidential Page 4 of 105

Ceragon Proprietary and Confidential Page 5 of 105

2.1 NetMaster Installation on Windows

2.1.1 NetMaster Server Pre-Installation for Windows

2.1.2 NetMaster Installation for Windows

Ceragon Proprietary and Confidential Page 6 of 105

NetMaster Install Sets

Install Unit Explanation

Server NetMaster Server.

SNMP Agent Northbound interface to higher-order network management systems

All install sets:

Install Set Explanation

Custom Pick one or more of all available install units.

2.1.2.2 New installation

Ceragon Proprietary and Confidential Page 7 of 105

Click Run to continue installation. An Internet Explorer Security Warning pop-up

Click Run to continue installation.

Ceragon Proprietary and Confidential Page 8 of 105

The Installer prepares to start:

Proceed by following the Installation wizard as follows:

Installation wizard in New installation mode

Click Next to continue the wizard.

Ceragon Proprietary and Confidential Page 9 of 105

Read the license agreement.

Ceragon Proprietary and Confidential Page 10 of 105

Ceragon Proprietary and Confidential Page 11 of 105

Press Next to continue.

Ceragon Proprietary and Confidential Page 12 of 105

Choose Install Folder step.

Click Next to continue.

Ceragon Proprietary and Confidential Page 13 of 105

Choose Shortcut Folder step.

Click Next to continue.

Ceragon Proprietary and Confidential Page 14 of 105

Pre Installation Summary step

Ceragon Proprietary and Confidential Page 15 of 105

Install Complete step.

Ceragon Proprietary and Confidential Page 16 of 105

Click Yes to open System Manager, and complete configuration of NetMaster,

2.1.2.3 Upgrade installation

Ceragon Proprietary and Confidential Page 17 of 105

Note: Action permissions for new functionality are default disabled

2.1.2.4 Maintenance installation

Ceragon Proprietary and Confidential Page 18 of 105

Installing step the existing NetMaster installation will be uninstalled before

2.1.3 System Manager Installation on Database Server

Ceragon Proprietary and Confidential Page 19 of 105

A database export will then work like this:

Ceragon Proprietary and Confidential Page 20 of 105

Click Run to continue installation.

Click Run to continue installation.

Ceragon Proprietary and Confidential Page 21 of 105

Proceed to install NetMaster by running the Installation wizard as follows:

Click Next to continue the wizard.

Ceragon Proprietary and Confidential Page 22 of 105

Read the license agreement.

Ceragon Proprietary and Confidential Page 23 of 105

Click Next to continue.