NetMaster Installation Guide

Download as pdf or txt
Download as pdf or txt
You are on page 1of 145

NetMaster NMS

Installation Guide

November 2013
Release: R13C01
Rev A

Copyright © 2013 by Ceragon Networks Ltd. All rights reserved.


NetMaster NMS R13C301 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 ("GPL License"). Inasmuch as such software is being used, it is released under the
GPL License, accordingly. Some software might have changed. The complete list of the software being
used in this product including their respective license and the aforementioned public available
changes is accessible on http://www.gnu.org/licenses/.

Information to User
Any changes or modifications of equipment not expressly approved by the manufacturer could void
the user’s authority to operate the equipment and the warranty for such equipment.

Revision History
Rev Date Author Description Approved by Date
A November 1, Charles Hurwitz First document Amir Matar November, 1,
2013 release for R13C01. 2013

Ceragon Proprietary and Confidential Page 2 of 145


NetMaster NMS R13C301 Installation Guide

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 NetMaster Client Installation for Solaris ....................................................................... 34
2.2.4 Uninstall NetMaster for Solaris ..................................................................................... 35
2.3 Post Installation ............................................................................................................ 36
2.3.1 NetMaster Server post installation ............................................................................... 36
2.4 Database Installation .................................................................................................... 41
2.4.1 NetMaster Database .................................................................................................... 41
2.4.2 Oracle ........................................................................................................................... 42
2.4.3 PostgreSQL .................................................................................................................. 71
2.5 High Availability Solution .............................................................................................. 84
2.5.1 NetMaster High Availability Solution ............................................................................ 84
2.5.2 Installation Instructions ................................................................................................. 88
2.5.3 Failover Procedure ....................................................................................................... 92
2.5.4 System Parameter Configuration ................................................................................. 92
2.5.5 Troubleshooting ............................................................................................................ 96
2.5.6 High-Availability Solution for Solaris .......................................................................... 103
2.6 External Documents ................................................................................................... 125
2.6.1 System Requirements ................................................................................................ 125
2.6.2 Technical Description ................................................................................................. 125

3. Appendix ....................................................................................................... 126


3.1 Supported NE types ................................................................................................... 126
3.2 Dictionary.................................................................................................................... 133

Ceragon Proprietary and Confidential Page 3 of 145


NetMaster NMS R13C301 Installation Guide

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 operator’s individual needs and requirements. With

Ceragon Proprietary and Confidential Page 4 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 5 of 145


NetMaster NMS R13C301 Installation Guide

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 or How to install Oracle if you need to install a
database server from scratch.
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.

Ceragon Proprietary and Confidential Page 6 of 145


NetMaster NMS R13C301 Installation Guide

Install Unit Explanation


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

All install sets:

Install Set Explanation


Client NetMaster Client only.

Server NetMaster Client, NetMaster Server, SNMP Agent and System Manager.

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.

Ceragon Proprietary and Confidential Page 7 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 8 of 145


NetMaster NMS R13C301 Installation Guide

The Installer prepares to start:

Proceed by following the NetMaster Installation wizard as follows:

NetMaster Installation wizard in New installation mode


The Introduction step displays some general information about the installation
process.

Click Next to continue the wizard.

Ceragon Proprietary and Confidential Page 9 of 145


NetMaster NMS R13C301 Installation Guide

Read the license agreement.

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

Ceragon Proprietary and Confidential Page 10 of 145


NetMaster NMS R13C301 Installation Guide

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

\
Click Next to continue.

Ceragon Proprietary and Confidential Page 11 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 12 of 145


NetMaster NMS R13C301 Installation Guide

Choose Install Folder step.


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

Click Next to continue.

Ceragon Proprietary and Confidential Page 13 of 145


NetMaster NMS R13C301 Installation Guide

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

Click Next to continue.

Ceragon Proprietary and Confidential Page 14 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 15 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 16 of 145


NetMaster NMS R13C301 Installation Guide

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.
Ceragon Proprietary and Confidential Page 17 of 145
NetMaster NMS R13C301 Installation Guide

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.
Proceed with the NetMaster Post installation steps.

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)

Ceragon Proprietary and Confidential Page 18 of 145


NetMaster NMS R13C301 Installation Guide

 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.
Proceed with the NetMaster Post installation steps.

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.)

Ceragon Proprietary and Confidential Page 19 of 145


NetMaster NMS R13C301 Installation Guide

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:\NetMaster\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:\NetMaster\Backup\Database on the
NetMaster server.
Note: If System Manager is not installed on the database server, the
database backup and restore feature in System Manager is not
available.

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.
Insert the CD into the desired drive and run the Setup.exe file to launch the
NetMaster Installer home page
Press the Install NetMaster button to initiate System Manager installation.
Internet Explorer needs to be told to run the installer:

Click Run to continue installation.

Ceragon Proprietary and Confidential Page 20 of 145


NetMaster NMS R13C301 Installation Guide

Internet Explorer needs to know that you trust the installer:

Click Run to continue installation.


The Installer is preparing to start:

Proceed to install NetMaster by running the NetMaster Installation wizard as


follows:

Ceragon Proprietary and Confidential Page 21 of 145


NetMaster NMS R13C301 Installation Guide

The Introduction step displays some general information about the installation
process

Click Next to continue the wizard.


Read the license agreement.

Ceragon Proprietary and Confidential Page 22 of 145


NetMaster NMS R13C301 Installation Guide

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.

Click Next to continue.

Ceragon Proprietary and Confidential Page 23 of 145


NetMaster NMS R13C301 Installation Guide

Choose Install Folder step.


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

Click Next to continue.

Ceragon Proprietary and Confidential Page 24 of 145


NetMaster NMS R13C301 Installation Guide

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.

Click Next to continue.

Ceragon Proprietary and Confidential Page 25 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 26 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 27 of 145


NetMaster NMS R13C301 Installation Guide

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:
4 On the database server, go to the folder:
<NetMaster_installation>/SystemManager/conf/system/
5 Open the file:
string@DatabaseBackupPath.xml
6 Change the path to another existing location and save the file

Ceragon Proprietary and Confidential Page 28 of 145


NetMaster NMS R13C301 Installation Guide

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 NetMaster Uninstaller wizard:

Click Uninstall to continue the wizard. A confirmation dialog appears:

Click Yes to confirm NetMaster removal.

Ceragon Proprietary and Confidential Page 29 of 145


NetMaster NMS R13C301 Installation Guide

NetMaster is now uninstalled:

Click Done to exit the NetMaster Uninstaller wizard.

Ceragon Proprietary and Confidential Page 30 of 145


NetMaster NMS R13C301 Installation Guide

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.
Ensure that the java binary directory is in PATH:
java -version
If version is not 1.6, do the following (assuming you have version 1.6.0.20):
cd /usr
rm java
ln -s /usr/jdk/jdk1.6.0_20 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:
7 Install ant (unpack the archive from folder /ant on installation media) on a file
system with enough space.
8 Create a symbolic link:
ln -s <Ant install folder>/apache-ant-1.8.1/bin/ant /usr/bin/ant

Ceragon Proprietary and Confidential Page 31 of 145


NetMaster NMS R13C301 Installation Guide

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

All install sets:


Install Set Explanation
Server NetMaster Server, SNMP Agent and System Manager.

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


Execute the installer as root
If installing from CD, insert the CD into the desired drive and do the following:
cd <folder mounted to CD drive>/Disk1/InstData/NoVM/
sh Setup.bin

Ceragon Proprietary and Confidential Page 32 of 145


NetMaster NMS R13C301 Installation Guide

If installing from zip-file, unpack the NetMaster installer netmaster-sol_R****.zip to


a temporary folder and do the following:
cd <temporary folder>/Disk1/InstData/NoVM/
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 NetMaster Initial Setup
wizard to set up NetMaster Server with a database schema.

Ceragon Proprietary and Confidential Page 33 of 145


NetMaster NMS R13C301 Installation Guide

2.2.3 NetMaster Client Installation for Solaris


The following chapter guides you through NetMaster Client installation on Solaris
platform.
NetMaster Client is supported on SUN Solaris 10 operating system and SPARC
platform.
Please note that this guide for manual installation of NetMaster Client is the only
supported installation procedure for Solaris.

2.2.3.1 Pre Installation Steps

Prepare Java
Ensure that a Java 2 Standard Edition JRE (or JDK), version 1.6 is installed on the
Solaris machine. Select 32-bit or 64-bit depending on your system configuration.
Java Runtime Environment (JRE) can be downloaded free of charge from
http://www.java.com/download. Installation Instructions can be found at
http://java.sun.com/javase/6/webnotes/install/jre/install-solaris.html.
Ensure that the java binary directory is in PATH
java -version
If version is not 1.6, do (example with 1.6.0.20 JRE installed at /usr/jre):
cd /usr
rm java
ln -s /usr/jre/jre1.6.0_20 java

2.2.3.2 Installation Steps


Insert the NetMaster CD into the desired drive and locate the directory Solaris.
Unzip the file netmaster.client.solaris.gtk.sparc.zip or net_0001.zip from CD into a
directory where you want NetMaster client to be installed (example
/usr/NetMaster/GUI Client/).
The following file structure will appear in the NetMaster client directory:

Set the execute permissions on the NetMaster binary file:


chmod +x NetMaster

Ceragon Proprietary and Confidential Page 34 of 145


NetMaster NMS R13C301 Installation Guide

The NetMaster Client can now be started by running the NetMaster executable.
See the chapter on NetMaster GUI Client for more details.

2.2.4 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/nera/

Ceragon Proprietary and Confidential Page 35 of 145


NetMaster NMS R13C301 Installation Guide

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.

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

Ceragon Proprietary and Confidential Page 36 of 145


NetMaster NMS R13C301 Installation Guide

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:
9 In the NetMaster System Manager: open the Settings menu and click
NetMaster Server.
10 Change the default value for Maximum Heap Size to a new value. i.e. 1400.
11 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 GUI clients to the server, and the computer’s firewall is
enabled, it is necessary to configure the firewall to allow these ports to be opened:
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 3387 JBoss EJB 3 socket based invoker layer
TCP port 4446 JBoss EJB3 remote method invocation

In order for NetMaster server to act as a FTP server the following ports must be
opened:
Port Description
TCP port 20 FTP - File Transfer [default data]
TCP port 21 FTP - File Transfer [Control]

Ceragon Proprietary and Confidential Page 37 of 145


NetMaster NMS R13C301 Installation Guide

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:


12 Open the Windows Firewall in the Windows Control Panel
13 In the General tab, make sure that On (recommended) is selected and that
Don’t allow exceptions is not checked.
14 In the Exceptions tab, click the Add Port. Repeat for all ports to allow.
15 Type the name, i.e. “NetMaster JNDI Port”.
16 Type the port number, i.e. “1098”.
17 Make sure that TCP is selected.
18 If you want to limit the IP addresses that is allowed to connect using this port,
click the Change scope button:

Ceragon Proprietary and Confidential Page 38 of 145


NetMaster NMS R13C301 Installation Guide

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.
19 Click OK
20 Click OK
21 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 NetMaster 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.

Ceragon Proprietary and Confidential Page 39 of 145


NetMaster NMS R13C301 Installation Guide

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 an Oracle 11G Release 2 database, 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\NetMaster\log
Example for Windows:
C:\Program Files\NetMaster\Server\JBoss-4.2.3\server\NetMaster\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\NetMaster\license\*.key

Ceragon Proprietary and Confidential Page 40 of 145


NetMaster NMS R13C301 Installation Guide

 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:\NetMaster\Backup\Database
 NetMaster Client parameters for external applications. The local application
path for the external applications is stored on each respective windows user
profiles and NetMaster username on the NetMaster clients:
C:\Documents and Settings\<Windows user name>\.NetMaster\.<NetMaster
username>\.metadata\.plugins\org.eclipse.core.runtime\.settings\no.nera.netw
orks.ngnms.richclient.configuration.prefs

2.4 Database Installation

2.4.1 NetMaster Database


NetMaster requires an Oracle or PostgreSQL database to be installed and available
for NetMaster use. Installation guides for how to install Oracle and PostgreSQL on
Windows platform are provided.
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.

Ceragon Proprietary and Confidential Page 41 of 145


NetMaster NMS R13C301 Installation Guide

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 How to Install Oracle


This section describes the installation steps for different editions of the Oracle
Database Server:
Installing Standard Edition One, Standard Edition and Enterprise Edition

Standard Edition One, Standard Edition and Enterprise Edition


This installation guide describes the steps of installing version 10g, 11g Release1
and 11g Release2 of the Oracle Database Server. Note that other versions of Oracle
may have a slightly different installation procedure, but the basic choices are the
same. The installation wizard contains a good Help function, thus the various
options will not be explained in detail in this guide.
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:

Ceragon Proprietary and Confidential Page 42 of 145


NetMaster NMS R13C301 Installation Guide

 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.
See the following links on how to install Oracle 10G , how to install Oracle 11G
Release1 and how to install Oracle 11G Release2. If you want to upgrade your
Oracle version, please read Oracle Database Version Upgrade first.

2.4.2.2 Oracle 10G Installation Procedure


The installation Wizard will guide you through the installation. You may cancel the
installation at any step until the wizard starts installing the files.
The database server must have been configured with fixed IP before you proceed, see
subchapter about Installing a loopback adapter.
Insert the CD into the desired drive and run the Setup.exe file to launch the
installation wizard. For the Basic Installation, select the Installation Type, enter
the Global Database Name and password for the administrative user accounts.
The Global Database Name must be a unique name in your LAN. A suggested
approach is to use a dot notation to compose a unique name from a local database
name and the computer name. The local database name is called System Identifier
(SID). The name before the first “.” is then automatically assigned as the SID name.
Note: Remember the SID and password for the SYSTEM user, as they
are used later in the Oracle Connection Info step during the
NetMaster Server installation. The password is case sensitive as
from Oracle 11G when enhanced security settings are enabled.

Ceragon Proprietary and Confidential Page 43 of 145


NetMaster NMS R13C301 Installation Guide

Click Next to continue.

Ceragon Proprietary and Confidential Page 44 of 145


NetMaster NMS R13C301 Installation Guide

Product-Specific Prerequisite Checks. Checks whether all hardware and software


requirements are met. If there are any problems reported you should read the
summary carefully. Note that there are some pre-install actions to perform if you
are using DHCP, the computer is not connected, or there are multiple network
connections installed.

Click Next to continue.

Ceragon Proprietary and Confidential Page 45 of 145


NetMaster NMS R13C301 Installation Guide

Summary. Displays a summary of the selections made above. Click Install to


continue.

Click Install to continue.

Ceragon Proprietary and Confidential Page 46 of 145


NetMaster NMS R13C301 Installation Guide

Installation. Displays the installation progress.

Click Next to continue

Ceragon Proprietary and Confidential Page 47 of 145


NetMaster NMS R13C301 Installation Guide

Configuration Assistant. Creates your database server instance and configures it


according to your selections above.

Ceragon Proprietary and Confidential Page 48 of 145


NetMaster NMS R13C301 Installation Guide

The Password Management dialog lets you configure the default user accounts.
Since you’ve already provided a password for the administrator accounts you
don’t need to do any changes here. Click OK to continue.

Ceragon Proprietary and Confidential Page 49 of 145


NetMaster NMS R13C301 Installation Guide

End of Installation. The installation is completed. Click Exit to close the installer,
and confirm in the message box that pops up.

2.4.2.3 Oracle 11G Release 1 Installation Procedure


The installation Wizard will guide you through the installation. You may cancel the
installation at any step until the wizard starts installing the files.
The database server must have been configured with fixed IP before you proceed, see
subchapter about Installing a loopback adapter.
Insert the CD into the desired drive and run the Setup.exe file to launch the
installation wizard. For the Basic Installation, select the Installation Type, enter
the Global Database Name and password for the administrative user accounts.

Ceragon Proprietary and Confidential Page 50 of 145


NetMaster NMS R13C301 Installation Guide

The Global Database Name must be a unique name in your LAN. A suggested
approach is to use a dot notation to compose a unique name from a local database
name and the computer name. The local database name is called System Identifier
(SID). The name before the first “.” is then automatically assigned as the SID name.
Note: Remember the SID and password for the SYSTEM user, as they
are used later in the Oracle Connection Info step during the
NetMaster Server installation. The password is case sensitive as
from Oracle 11G when enhanced security settings are enabled.

Ceragon Proprietary and Confidential Page 51 of 145


NetMaster NMS R13C301 Installation Guide

Product-Specific Prerequisite Checks. Checks whether all hardware and software


requirements are met. If there are any problems reported you should read the
summary carefully. Note that there are some pre-install actions to perform if you
are using DHCP, the computer is not connected, or there are multiple network
connections installed.

Click Next to continue.

Ceragon Proprietary and Confidential Page 52 of 145


NetMaster NMS R13C301 Installation Guide

Oracle Configuration Manager Registration.

Click Next to continue

Ceragon Proprietary and Confidential Page 53 of 145


NetMaster NMS R13C301 Installation Guide

Summary. Displays a summary of the selections made above.

Click Install to continue.

Ceragon Proprietary and Confidential Page 54 of 145


NetMaster NMS R13C301 Installation Guide

Installation. Displays the installation progress.

Click Next to continue

Ceragon Proprietary and Confidential Page 55 of 145


NetMaster NMS R13C301 Installation Guide

Configuration Assistant. Creates your database server instance and configures it


according to your selections above.

Ceragon Proprietary and Confidential Page 56 of 145


NetMaster NMS R13C301 Installation Guide

The Password Management dialog lets you configure the default user accounts.
Since you’ve already provided a password for the administrator accounts you
don’t need to do any changes here.

Click OK to continue.

Ceragon Proprietary and Confidential Page 57 of 145


NetMaster NMS R13C301 Installation Guide

End of Installation. The installation is completed. Press Exit to close the installer,
and confirm in the message box that pops up.

2.4.2.4 Oracle 11G Release 2 Installation Procedure


The installation Wizard will guide you through the installation. You may cancel the
installation at any step until the wizard starts installing the files.
The database server must have been configured with fixed IP before you proceed, see
subchapter about Installing a loopback adapter.
First insert the CD into the desired drive and run the Setup.exe file to launch the
installation wizard.

Ceragon Proprietary and Confidential Page 58 of 145


NetMaster NMS R13C301 Installation Guide

Configure Security Updates. Select email information if desired.

Click Next to continue.


Installation Option. Select Create and configure a database.

Click Next to continue.

Ceragon Proprietary and Confidential Page 59 of 145


NetMaster NMS R13C301 Installation Guide

System Class. Select according to the class of system hosting oracle database.

Click Next to continue.


Grid Installation Options. Select according to the system hosting oracle database.

Click Next to continue.

Ceragon Proprietary and Confidential Page 60 of 145


NetMaster NMS R13C301 Installation Guide

Install Type. Select Advanced Install if you want additional configuration during
install.

Click Next to continue.

Ceragon Proprietary and Confidential Page 61 of 145


NetMaster NMS R13C301 Installation Guide

Select the Database Edition and enter the Global Database Name and password
for the administrative user accounts.
The Global Database Name must be a unique name in your LAN. A suggested
approach is to use a dot notation to compose a unique name from a local database
name and the computer name. The local database name is called System Identifier
(SID). The name before the first “.” is then automatically assigned as the SID name.
Note: Remember the SID and password for the SYSTEM user, as they
are used later in the Oracle Connection Info step during the
NetMaster Server installation. The password is case sensitive as
from Oracle 11G when enhanced security settings are enabled.

Click Next to continue.

Ceragon Proprietary and Confidential Page 62 of 145


NetMaster NMS R13C301 Installation Guide

Prerequisite Checks. Checks whether all hardware and software requirements are
met. If there are any problems reported you should read the summary carefully.
Note that there are some pre-install actions to perform if you are using DHCP, the
computer is not connected, or there are multiple network connections installed.

Wait for checks to complete.

Ceragon Proprietary and Confidential Page 63 of 145


NetMaster NMS R13C301 Installation Guide

Summary. Displays a summary of the selections made above. Please verify settings
and Database information, including SID

Click Finish to start installation.


Installation Product. Displays the installation progress.

Wait for installation to complete.

Ceragon Proprietary and Confidential Page 64 of 145


NetMaster NMS R13C301 Installation Guide

Database Configuration Assistant. Creates your database server instance and


configures it according to your selections above.

Wait for database creation to complete.

Ceragon Proprietary and Confidential Page 65 of 145


NetMaster NMS R13C301 Installation Guide

Database creation complete.


The Password Management dialog lets you configure the default user accounts.
Since you’ve already provided a password for the administrator accounts you
don’t need to do any changes here.

Click OK to continue.

Ceragon Proprietary and Confidential Page 66 of 145


NetMaster NMS R13C301 Installation Guide

Finish Installation. The installation is completed

Click Close to exit the installer.

Prevent Oracle password expiry


Please be aware that Oracle 11G sets password expiry by default to 180 days. To
avoid that NetMaster server stops due to expired password, set password life time
to unlimited, as follows:
22 Log into i.e. SQLPLUS with SYSDBA privileges. (sqlplus / as SYSDBA)
23 Run the sql commands below which will prevent that password will expire
ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED
PASSWORD_LIFE_TIME UNLIMITED;
commit;

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.
Ceragon Proprietary and Confidential Page 67 of 145
NetMaster NMS R13C301 Installation Guide

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:
24 Open the Windows Control Panel.
25 Double-click Add Hardware to start the Add Hardware wizard.
26 In the Welcome window, click Next.
27 In the Is the hardware connected? window, select Yes, I have already
connected the hardware, and click Next.
28 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.
29 In the wizard can help you install other hardware window, select Install the
hardware that I manually select from a list, and click Next.
30 From the list of hardware types, select the type of hardware you are installing
window, select Network adapters, and click Next.
31 In the Select Network Adapter window, make the following selections:
Manufacturer: Select Microsoft.
Network Adapter: Select Microsoft Loopback Adapter.
Click Next.
32 In the wizard is ready to install your hardware window, click Next.
33 In the Completing the Add Hardware Wizard window, click Finish.
Note: If using Windows 2003, restart the computer now.
34 Right-click My Network Places on the desktop and choose Properties. This
displays the Network Connections Control Panel.
35 Right-click the connection that was just created. This is usually named "Local
Area Connection 2". Choose Properties.
36 On the General tab, select Internet Protocol (TCP/IP), and click Properties.
37 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.
38 Leave all other fields empty.
39 Click OK.
40 Click OK.
41 Close Network Connections.
42 Restart the computer.

Ceragon Proprietary and Confidential Page 68 of 145


NetMaster NMS R13C301 Installation Guide

43 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 16.
hostname is the name of the computer.
domainname is the name of the domain.

For example: 10.10.10.10 mycomputer.mydomain.com mycomputer


44 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


45 To set the ORACLE_HOSTNAME environment variable:
46 Display System in the Windows Control Panel.
47 In the System Properties dialog box, click Advanced.
48 In the Advanced tab, click Environment Variables.
49 In the Environment Variables dialog box, under System Variables, click New.
50 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.

Ceragon Proprietary and Confidential Page 69 of 145


NetMaster NMS R13C301 Installation Guide

51 Click OK, then in the Environment Variables dialog box, click OK.
52 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 organization’s security policy. In order to overcome this follow the steps
below to avoid using the database administration credentials during the
NetMaster installation.
Create the Oracle user manually by following the steps below:
53 Log into ie. SQLPLUS with SYSTEM privileges. (sqlplus
SYSTEM/password@sid)
54 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;
55 Start the NetMaster installation
56 Reinitialize existing (overwrite): The installer will delete the content of the
existing database schema and reinitialize it.
57 Continue the installation.

Oracle Database Version Upgrade


This section describes how to upgrade from previous Oracle versions to a newer
Oracle version. Note that this is only one of several Oracle database upgrade
strategies.
This procedure applies to upgrade between these versions:
 Oracle 10g --> Oracle 11g Release 1
 Oracle 10g --> Oracle 11g Release 2
 Oracle 11g Release 1 --> Oracle 11G Release 2
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:
58 Use System Manager to perform a backup of the database schemas/users to
keep.
59 Stop NetMaster Server if running
60 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)
Ceragon Proprietary and Confidential Page 70 of 145
NetMaster NMS R13C301 Installation Guide

61 Install the new version of Oracle. (See Oracle installation procedure for Oracle
11g Release 1 or Oracle 11g Release 2)
62 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.
63 Use System Manager to remove all scheduled backup tasks.
64 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).
65 Use System Manager to create new scheduled backup tasks as desired.

2.4.2.5 Post Installation Settings


Run the following command after installation:
ALTER SYSTEM SET OPEN_CURSORS=3000'*'SCOPE=MEMORY;
ALTER SYSTEM SET OPTIMIZER_MODE=FIRST_ROWS;

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. For your convenience we
have embedded PostgreSQL version 9.1.3 Windows x64 as well as PostgreSQL
documentation on the NetMaster installation CD. You will find it in the PostgreSQL
directory.
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.

Ceragon Proprietary and Confidential Page 71 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 72 of 145


NetMaster NMS R13C301 Installation Guide

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

Click Next to continue.

Ceragon Proprietary and Confidential Page 73 of 145


NetMaster NMS R13C301 Installation Guide

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.

Click Next to continue.

Ceragon Proprietary and Confidential Page 74 of 145


NetMaster NMS R13C301 Installation Guide

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:
66 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.
67 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.
68 Continue the installation with PostgreSQL

Ceragon Proprietary and Confidential Page 75 of 145


NetMaster NMS R13C301 Installation Guide

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.

Click Next to continue.

Ceragon Proprietary and Confidential Page 76 of 145


NetMaster NMS R13C301 Installation Guide

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.

Click Next to continue.

Ceragon Proprietary and Confidential Page 77 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 78 of 145


NetMaster NMS R13C301 Installation Guide

Ceragon Proprietary and Confidential Page 79 of 145


NetMaster NMS R13C301 Installation Guide

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:
69 Start the pgAdmin tool. You will find it in Start | All programs | PostgreSQL 9.1
| pgAdmin III.
70 Connect to your PostgreSQL database server.

Ceragon Proprietary and Confidential Page 80 of 145


NetMaster NMS R13C301 Installation Guide

71 Expand the following in the left window: PostgreSQL Database Server ->
Databases -> Postgres.
72 Choose Tools | Server Configuration | postgresql.conf.
73 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.
74 Click OK.

Ceragon Proprietary and Confidential Page 81 of 145


NetMaster NMS R13C301 Installation Guide

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

75 In the pgAdmin tool choose File | Save.


76 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.
77 Choose Tools | Server configuration | pg_hba.conf.
78 Add an entry with IP-address and subnet mask of the client that shall be
allowed access to the database server.

Ceragon Proprietary and Confidential Page 82 of 145


NetMaster NMS R13C301 Installation Guide

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


79 In the pgAdmin tool choose File | Save.
80 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.
81 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


82 Stop NetMaster Server
83 Upgrade NetMaster Server and NetMaster System Manager to latest release
84 Cancel wizard for upgrading database after upgrading NetMaster and System
Manager.
85 Perform a backup of current PostgreSQL database by starting the Backup
Active User/Schema wizard from the Administration | Database Tasks view in
System Manager.
86 Uninstall current version of PostgreSQL. Start ? Control Panel ? Add Remove
Programs. Select PostgreSQL 8.3 and click Remove. Follow the instructions.
87 If the directory C:\Program Files\PostgreSQL\8.3 still exists, it can now be
removed, since it is not in use anymore
88 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
89 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.

Ceragon Proprietary and Confidential Page 83 of 145


NetMaster NMS R13C301 Installation Guide

90 Upgrade database by starting the Upgrade User/Schema wizard from the


Administration->Database Tasks view in System Manager.
91 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.

Ceragon Proprietary and Confidential Page 84 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 85 of 145


NetMaster NMS R13C301 Installation Guide

NetMaster system with replication

In case of failure, you will need to:


92 Manually log all clients off the Primary NetMaster server and log them into the
Standby NetMaster server.
93 Stop the exports from the Primary database server and the scheduled imports
on the Standby database server.
94 When the Primary server is fixed, create a backup of the Standby database
server and import the data to the Primary database server.
95 Manually log all clients off the Standby NetMaster server and log them into the
Primary NetMaster server.
96 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*
 PostgreSQL 8.3.5.1**
* Requires NetMaster R13A00 or later version
** Requires NetMaster version prior to R13A00
This high availability solution support the following NetMaster server
configurations
 1+1 HA Configuration
 2+1 HA Configuration

Ceragon Proprietary and Confidential Page 86 of 145


NetMaster NMS R13C301 Installation Guide

 2+2 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.

Ceragon Proprietary and Confidential Page 87 of 145


NetMaster NMS R13C301 Installation Guide

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


Install Java JRE on both the Primary and Standby database servers. The Java JRE
can be downloaded from the web or copied from the NetMaster installation from
one of the NetMaster servers where NetMaster is installed.
To download the current Java Runtime environment (JRE), go to the following
web page:
http://www.oracle.com/technetwork/java/javase/downloads/
If the Java JRE is downloaded from Oracle and installed:
97 Open a command prompt (cmd)
98 Verify that Java is running (the Java path is specified in the Environment
variables section).
99 At the cmd prompt, type java –version.
If the Java JRE was copied from the NetMaster installation, manually set the home
path of the Java installation:
100 Click My Computer > System Properties > Advanced > Environment
Variables > System Variables, and scroll down and select the Path variable. If
the home path of Java does not appear, add it to the path:
101 Add a semicolon (;) and the corresponding Java home path for the
compression tool used by NetMaster at the end of the current Variable value
field.
An example of the required Java home path is:
C:\Program Files\Nera\NetMaster\jre\bin

Ceragon Proprietary and Confidential Page 88 of 145


NetMaster NMS R13C301 Installation Guide

102 Verify that Java is running (i.e., the Java path specified in the Environment
variables is correct) by open a command prompt (cmd) and type java -
version.

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.
103 On both the Primary and Standby database servers, create the following
folder: C:\NetMaster.
104 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 \\”PrimaryNetMasterServerIP”stop "NetMaster"
sc \\”PrimaryNetMasterServerIP”start "NetMaster"
2 On the Standby database system, open command prompt and run the following
commands:
sc \\”StandbyNetMasterServerIP”stop "NetMaster"
sc \\”StandbyNetMasterServerIP”start "NetMaster"

Ceragon Proprietary and Confidential Page 89 of 145


NetMaster NMS R13C301 Installation Guide

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
105 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.
106 On the Standby database server, create and share the folder:
.\tasks\backup\
Give everyone full rights to modify the content (see Sharing folders).
107 On the Primary database server, create and share the folder:
.\tasks\backup\
Give everyone full rights to modify the content (see Sharing folders).
108 On the Primary database server, open the file
ha_netmaster_environment.cmd batch script in a text editor (Notepad).
109 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.>
110 On the Standby database server, open the file
ha_netmaster_environment.cmd batch script in a text editor (Notepad).
111 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.>
112 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.

Ceragon Proprietary and Confidential Page 90 of 145


NetMaster NMS R13C301 Installation Guide

113 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:
114 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.
115 On the Standby database server, execute the
ha_restore_netmaster_database.cmd task (right-click and select Run for the
scheduled service).
116 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.

Ceragon Proprietary and Confidential Page 91 of 145


NetMaster NMS R13C301 Installation Guide

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:
117 Manually log all clients onto the Standby NetMaster server.
118 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.
119 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)

Ceragon Proprietary and Confidential Page 92 of 145


NetMaster NMS R13C301 Installation Guide

Parameter name Default value / Comment


<type>
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 user.
PASSWORD% By default this is the same as the ADMIN
(SYSTEM) password.
DB_TYPE <string> Database type definition:
 Oracle: ORACLE
 PostgreSQL: POSTGRESQL
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.

Ceragon Proprietary and Confidential Page 93 of 145


NetMaster NMS R13C301 Installation Guide

2.5.4.2 Database export parameters


The database export parameters are located in the file:
netmaster_environment.cmd.
Parameter name Default value / Comment
<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:
netmaster_environment.cmd.
Parameter name Default value / Comment
<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.
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%

Ceragon Proprietary and Confidential Page 94 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 95 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 96 of 145


NetMaster NMS R13C301 Installation Guide

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
120 Make sure that all required services are activated on both servers.
121 In the Windows Control Panel > Network Connections, right-click and
select Properties for the active LAN connection.
122 Ensure that the following items are enabled:
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
Internet Protocol (TCP/IP)
123 Under Internet Protocol (TCP/IP) > Properties, make sure the IP address
settings are correct.

Ceragon Proprietary and Confidential Page 97 of 145


NetMaster NMS R13C301 Installation Guide

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.
124 Right-click the backup folder and select Share with > Specific people.
Share with specific people

125 Select Everyone and click Add.


126 Change the permission level to Read/Write.

Ceragon Proprietary and Confidential Page 98 of 145


NetMaster NMS R13C301 Installation Guide

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 user’s password, or scheduled tasks
will fail.
1 In the Create a Basic Task Wizard, enter the name and description (optional)
of the task.

Ceragon Proprietary and Confidential Page 99 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 100 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 101 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 102 of 145


NetMaster NMS R13C301 Installation Guide

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 \\”NetMasterServerIP”stop "NetMaster"
sc \\”NetMasterServerIP”start "NetMaster"
 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.

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.

Ceragon Proprietary and Confidential Page 103 of 145


NetMaster NMS R13C301 Installation Guide

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:
127 Stop the NetMaster server
128 Rename local backup files
129 Restore the database with the latest backup
130 Start NetMaster server

Ceragon Proprietary and Confidential Page 104 of 145


NetMaster NMS R13C301 Installation Guide

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)

Ceragon Proprietary and Confidential Page 105 of 145


NetMaster NMS R13C301 Installation Guide

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


131 On both db1 and db2 hosts:
132 Log in as ha.
133 Run ssh-keygen -t rsa
134 Click Enter in response to questions.
135 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)

Ceragon Proprietary and Confidential Page 106 of 145


NetMaster NMS R13C301 Installation Guide

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)
136 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
137 On db1 host, copy the file ha.zip to a folder accessible by the ha user.
138 Log in to db1 as ha.
139 unzip ha.zip to the home folder.
140 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
141 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
142 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

Ceragon Proprietary and Confidential Page 107 of 145


NetMaster NMS R13C301 Installation Guide

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 it’s necessary to specify the host ip address, do the
following:
143 On db1 and db2 hosts, log in as ha.
144 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

Ceragon Proprietary and Confidential Page 108 of 145


NetMaster NMS R13C301 Installation Guide

145 Determine which ip address is reached, when connecting from the other
end by executing the following command from the other end: ping <ip-
address>
146 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 user’s
netmaster-ha/exports directory, and to allow user ha to run export/import,
do the following on both db host machines:
147 While logged in as root user, type usermod -G oinstall ha
148 Logout user ha and login as user ha again (this is to let usermod take
effect).
149 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>)
)
)

Ceragon Proprietary and Confidential Page 109 of 145


NetMaster NMS R13C301 Installation Guide

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 NetMaster -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

Ceragon Proprietary and Confidential Page 110 of 145


NetMaster NMS R13C301 Installation Guide

 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

Ceragon Proprietary and Confidential Page 111 of 145


NetMaster NMS R13C301 Installation Guide

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-ha/exports Base dir for exports. local exports will be kept
here. Remote exports will be kept in subdir
“remote”

Ceragon Proprietary and Confidential Page 112 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 113 of 145


NetMaster NMS R13C301 Installation Guide

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 don’t 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
Ceragon Proprietary and Confidential Page 114 of 145
NetMaster NMS R13C301 Installation Guide

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 don’t 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
Ceragon Proprietary and Confidential Page 115 of 145
NetMaster NMS R13C301 Installation Guide

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:
150 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.
151 Perform a switchover.
152 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 :
153 Perform a switchover.
154 Inform NetMaster users to logon to the other NetMaster server
155 Fix or replace the broken host, re-install and re-configure software.

Ceragon Proprietary and Confidential Page 116 of 145


NetMaster NMS R13C301 Installation Guide

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

Ceragon Proprietary and Confidential Page 117 of 145


NetMaster NMS R13C301 Installation Guide

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
You should receive the following message:
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
You should receive the following message:
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

Ceragon Proprietary and Confidential Page 118 of 145


NetMaster NMS R13C301 Installation Guide

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 ""

Ceragon Proprietary and Confidential Page 119 of 145


NetMaster NMS R13C301 Installation Guide

/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.
Ceragon Proprietary and Confidential Page 120 of 145
NetMaster NMS R13C301 Installation Guide

Problem: Cannot find samba net program


The command which net returns:
no net in /usr/sbin /usr/bin ...
Solution:
156 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

157 Search for the net program as follows:


find / -name net -print |grep sfw
158 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.

Ceragon Proprietary and Confidential Page 121 of 145


NetMaster NMS R13C301 Installation Guide

If the file doesn’t 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

Ceragon Proprietary and Confidential Page 122 of 145


NetMaster NMS R13C301 Installation Guide

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:
159 Check values in ha-env.sh for:
HA1_DB_ADMIN_USER
HA1_DB_ADMIN_PASSWORD
HA2_DB_ADMIN_USER
Ceragon Proprietary and Confidential Page 123 of 145
NetMaster NMS R13C301 Installation Guide

HA2_DB_ADMIN_PASSWORD
160 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>

Ceragon Proprietary and Confidential Page 124 of 145


NetMaster NMS R13C301 Installation Guide

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.

Ceragon Proprietary and Confidential Page 125 of 145


NetMaster NMS R13C301 Installation Guide

3. Appendix

3.1 Supported NE types


NetMaster supports the following network elements:

3.1.1.1 FibeAir IP-10 family


FibeAir IP-10 family is a carrier-grade, wireless Ethernet backhaul product line.
The series includes both TDM and Ethernet high capacity devices. All products in
the FibeAir family are tightly coupled with Ceragon’s advanced microwave radio
and are fully managed by a state-of-the-art management system to provide a full
solution for mobile backhaul, private networks and last mile wireline networks.
The FibeAir IP-10 supports the entire licensed spectrum – from 6GHz to 42GHz
and on all the approved ETSI and FCC channels. The product line offers wide
capacity ranges from 10Mbps to 1Gbps per radio carrier along with enhanced
power adaptive ACM (Adaptive Coding & Modulation), Cross Polarization
Interference Canceller (XPIC), asymmetrical link support which improves
utilization and even header & payload compressions for maximum spectral
efficiency.

3.1.1.2 FibeAir IP-20N


FibeAir IP-20N is a highly modular and flexible cellular backhaul product that is
optimized for nodal deployment, with a small footprint, high density, and a high
degree of scalability and availability. An IP-20N system is based on a chassis,
which is provided in sizes that fit a single rack unit or two rack units, and which
contains five or ten slots for any mix of traffic and radio cards. IP-20N supports
any mix of Ethernet and TDM traffic cards.

3.1.1.3 FibeAir 2000 family


FibeAir 2000 is a carrier-class high-capacity sub-6 GHz backhaul solution that
enables carriers to accommodate capacity growth and maintain profitability
through unparalleled price/performance ratio. The high-capacity radio system
provides up to 200 Mbps aggregated throughput, with a flexible combination of
Ethernet and TDM with up to 16 E1/DS1 interfaces.
FibeAir 2500 series is a high capacity point-to-multipoint solution that delivers up
to 200 Mbps aggregated traffic. A FibeAir 2500 system utilizes base station units
(HBS) and subscriber units (HSU) as the building blocks for mobile applications
and networks that operate in the unlicensed frequency bands from 4.9 to 6 GHz.
The FibeAir 4800 product family carries Fast Ethernet and TDM services over
license exempt bands, effectively connecting voice and data over a single link. The
system ensures low BER, as well as low latency and full compliance with E1/T1
interface, jitter and wander requirements. FibeAir 4800 enables direct connection
of existing equipment, such as LANs and PBX systems, thereby eliminating the
need for additional external equipment.
Ceragon Proprietary and Confidential Page 126 of 145
NetMaster NMS R13C301 Installation Guide

3.1.1.4 FibeAir 3200T


FibeAir 3200T supports multiple capacities, frequencies, modulation schemes, and
configurations for various network requirements. FibeAir 3200T capacities
support up to 10 x SDH / SONET carriers (10 x 155 Mbps). In addition, a
redundant channel provides backup in the event of equipment failure or
degradation on specific frequency channels. FibeAir 3200T was designed to
provide maximum protection and availability for backbone networks. Featuring
N+1 switching protection, embedded space diversity, and ultra high power,
operators can greatly improve hop length, system performance and availability.

3.1.1.5 FibeAir 1500P


FibeAir 1500P is a versatile high-capacity point-to-point backhaul solution that
combines advanced features and capabilities in a single platform. 1500P provides
155 to 622 Mbps SDH/SONET and 50 to 800 Mbps Fast/Gigabit Ethernet
throughput, a frequency range of 6 to 38 GHz, and modulation schemes including
QPSK, 16, 32, 64, 128 and 256 QAM over 10-56 MHz channels.

3.1.1.6 FibeAir 1500R


In response to budget-conscious backhaul needs, and with high spectral efficiency,
availability, reliability (MTBF), and maintainability in mind, FibeAir 1500R
provides network builders and operators with a solution that can deliver from 45
to 622 Mbps in a single compact unit. The 1500R system offers a modulation
scheme of from 16 to 128 QAM over 28, 40, and 50/56 MHz channels, with 56
MHz channels operating in all frequency bands.

3.1.1.7 FibeAir 70F


FibeAir 70F is an all-outdoor wireless packet family of products featuring carrier-
grade, high-capacity support for the 71-76 and 81-86 GHz regulated E-Band.
Designed with stringent wireless backhaul requirements in mind, FibeAir 70T
seamlessly increases backhaul capacity, offering support for any topology,
including ring, mesh, or asymmetrical broadband applications.

3.1.1.8 FibeAir 70T


FibeAir 70T is an all-outdoor wireless packet family of products featuring carrier-
grade, high-capacity support for the 71-76 GHz regulated E-Band. Designed with
stringent wireless backhaul requirements in mind, FibeAir 70T seamlessly
increases backhaul capacity, offering support for any topology, including ring,
mesh, or asymmetrical broadband applications.

3.1.1.9 CityLink family


CityLink is a family of radio relay equipment for transmission of capacities from
STM-0 to STM-1 in the 5 to 38 GHz frequency bands with 32, 64, or 128TCM
modulation.
The CityLink can be configured with the Nera Configuration Manager application.

Ceragon Proprietary and Confidential Page 127 of 145


NetMaster NMS R13C301 Installation Guide

3.1.1.10 CompactLink
The CompactLink is fully a featured, microwave radio system for the global
telecommunications market. CompactLink IV operates in the frequency band 7, 8,
13, 15, 18 and 23 GHz, and with data rates of 4, 8 or 16 E1 or T1. It is designed for
transmission of voice, data and video traffic. Standardized data rates (E1/T1) and
frequency bands are approved by international organizations (FCC, ITU-R, ITU-T,
ETSI).
The CompactLink can be configured with the Nera Configuration Manager and
Telnet applications.

3.1.1.11 Evolution Series


The Evolution Series is a point-to-point microwave radio system in licensed
frequency bands from 5 GHz to 38 GHz. Its transmission capacity is scalable
between 6 Mb/s and 600 Mb/s based on a common software defined platform.

Evolution Series radios can be configured with a browser like Internet Explorer.
You can launch the Evolution Manager and the Evolution Manager in Default
Browser tools from NetMaster External Tools.

Evolution equipment model


Physical ports on evolution equipment are visible as PTPs (Physical Termination
Points) in the NetMaster equipment model.
The following figure is a side by side example of how ports on a 7+1 system is
translated in NetMaster, with the physical model to the left and the equipment
model to the right:

Ceragon Proprietary and Confidential Page 128 of 145


NetMaster NMS R13C301 Installation Guide

PTP names for evolution elements are constructed in NetMaster from the
corresponding location on the physical unit, using a frame.slot.port or
frame.slot.antenna direction. channel naming convention. This is illustrated for a
radio port in the following diagram:

The naming convention explains the previous 7+1 example as follows:


Ethernet ports: The unit consists of four frames, configured with an su card in
slot 1 in frame 1 providing four Ethernet ports. The four ethernet ports are visible
as four ethernet PTPs in the equipment model. Their labels in the NetMaster
model describe their positions in the physical unit.
For instance eth-1.1.2 indicates that this PTP corresponds to the physical port in
frame 1 (see evolution manual for frame numbering), slot 1 (see evolution manual
Ceragon Proprietary and Confidential Page 129 of 145
NetMaster NMS R13C301 Installation Guide

for slot numbering), port 2 (counting from the left on face of the card). In the
example the red color on this particular PTP indicates an alarm condition on the
particular port.
Radio ports: The unit is configured for transmitting on 8 radio channels in a
particular direction, “Antenna Direction 1.“ Of the radio channels, 7 are regular
channels, 1 is a protection channel. All this information can be read from the labels
of the PTPs.
For instance radio-3.5.Antenna Direction 1.5 indicates that this PTP
corresponds to the radio connected to the riu card in frame 3, slot 5. The radio is
transmitting in Antenna Direction 1 on channel 5. The identifier “Antenna
Direction 1” is a user configurable name read from the element. Channels are
numbered 1-7 or postfixed with P for protection. In the example, the yellow color
on this particular PTP indicates an alarm condition on the particular channel.
STM ports: The unit is also configured with 7 line-side, electrical 155Mb line
cards. There is one card in frame 1 (bottom), and two in each of the other frames.
The same rules apply for naming the stm PTPs as for ethernet ports and radio
connections.
For instance stm1-4.3 indicates that this PTP corresponds to the stm1 port
provided by the card in frame 4, slot 3.

Native naming
In some cases it may be desirable to see the native name of a resource shown in
NetMaster. For entities that has a direct equivalent in the NetMaster model (some
do not), the native name can be seen in the Properties view under the
nativeEMSName property.
The figure below shows an alarm on a resource in Evolution web configurator:

Ceragon Proprietary and Confidential Page 130 of 145


NetMaster NMS R13C301 Installation Guide

The figure below shows the alarm on an equivalent resource in NetMaster:

3.1.1.12 FlexLink
FlexLink is a low and medium capacity microwave access solution covering from
2x2 to 16x2 Mbit/s capacity, in the 7, 8, 13, 15, 18, 23, 26, 28, 32 and 38 GHz
frequency bands.
The FlexLink can be configured with the Flexman application.

3.1.1.13 InterLink family


InterLink is a family of scalable indoor mounted radio-relay equipment for
transmission of N x 155 Mbit/s in the frequency bands 4 - 11 GHz.
The InterLink can be configured with the Nera Configuration Manager application.

3.1.1.14 NetLink
Nera NetLink provides point-to-multipoint wireless access solutions for operators
in the broadband markets.
NetLink supplies reliable broadband data services in frequency bands from:
Product Gross bandwidth Frequency range NLOS
NetLink I 3 Mbps 0.9 to 5.8 GHz No
NetLink II 12 Mbps 3.5 GHz Yes
NetLink III 54 Mbps 5.2 and 5.8 GHz Yes

The Netlink can be configured with the NetLink I/II/III Configure applications.

Ceragon Proprietary and Confidential Page 131 of 145


NetMaster NMS R13C301 Installation Guide

3.1.1.15 SDH Mux BG-20/20E and BG-30/30E


The SDH Mux BG-20 is a compact Multi-Service Provisioning Platform with STM-1
and STM-4 capability and a capacity up to 16 VC4.
The extension shelf BG-20E provides additional slots for various traffic modules,
increasing the total interfacing capacity of the BG-20.
The SDH Mux BG-30 is a compact Multi-Service Provisioning Platform with STM-1,
STM-4 and STM-16 capability and a capacity up to 64 VC4.
The extension shelf BG-30E provides additional slots for various traffic modules,
increasing the total interfacing capacity of the BG-30.
The BG-20/BG-30 elements can be configured with the LCT-BGF and the EMS-BGF
applications.

3.1.1.16 SmartConnect
The SmartConnect is a hybrid Ethernet and SDH based device for grooming and
transporting packet data and voice (TDM) traffic in a Metro-Access-Network.
SmartConnect is supplied in variants with a transport capacity of 155 Mbps (STM-
1) or 622 Mbps (STM-4) configured either as a Terminal Multiplexer (TM) or
Add/Drop multiplexer (ADM).
The SmartConnect elements can be configured with the SmartManager
application.

3.1.1.17 SmartMetro
The SmartMetro consists of a low-cost shelf (compatible with 19" or ETSI racks)
with room for up to twenty-one plug-in modules. The plug-in slots can
accommodate modules of different types: :
 Two aggregate modules consisting of TDM matrix, Ethernet Crossbar system,
System controller and SDH interfaces.
 Eight tributary modules with a number of SDH, Ethernet and PDH interfaces.
 Eight connector modules with physical interfaces for PDH, SDH and fast
Ethernet.
 Fan, power and auxiliary modules.
The SmartMetro can be configured with the SmartManager application.

3.1.1.18 SmartNodeA / SmartNodeC


The SmartNode is an SDH multiplex system which supports different types of
transmission media. It can be used in networks based on fiber, radio or copper
media. The SmartNode concentrates both IP and TDM traffic and is able to
interface with both TDM and IP backbone networks. The SmartNode maps both IP
and TDM traffic into a TDM data stream or into an IP data stream.
The SmartNode elements can be configured with the SmartManager application.

Ceragon Proprietary and Confidential Page 132 of 145


NetMaster NMS R13C301 Installation Guide

3.1.1.19 SmartPack
SmartPack is a monitoring and control unit used in Minipack, Flatpack2 and
Powerpack power supply solutions offered by Eltek.
The SmartPack can be configured with the SmartPack Manager application.

3.1.1.20 WiLink I
WiLink I is based on the WiMAX platform and operates in the licensed 3.3 GHz and
3.5 GHz frequency bands. Channel bandwidths 1.75 MHz and 3.5 MHz.
The WiLink I can be configured with the WiLink Config application.

3.1.1.21 Discontinued Nera Networks radio products


NetMaster also supports older Nera Networks radio products that are still on the
market, but have been discontinued and replaced by newer products.
Discontinued products supported are:
 NL29x
 NL18x-A
 NL24x
These radios can be configured with the Nera Configuration Manager application.

3.2 Dictionary

1+1 HA Configuration
A High availability configuration with one primary server and one standby server.
NetMaster and database will run on both servers.

2+1 HA Configuration
A High availability configuration with two primary servers and one standby
server. NetMaster and database will 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 database will run separately on the primary servers and
separately on the standby server allowing maximum redundancy and
performance

Active Alarm
An alarm generated by a network element or system component which has the
"raised" alarm state. When the error condition is cleared, the alarm will no longer
be an active alarm. (corresponds to "Current Alarm" in Nera Configuration
Manager).

Ceragon Proprietary and Confidential Page 133 of 145


NetMaster NMS R13C301 Installation Guide

Administrative Domain
An administrative domain is used to group other resources in NetMaster. An
administrative domain can contain any other resource in the network, including
other administrative domains.

Alarm
A notification of a specific event. An alarm may or may not represent an error.

Application Server
A physical server that runs services for given purposes. NetMaster is typically
running on an application server.

Authentication
The process of validating the claimed identity of an end user or a device, such as a
host, server, switch, router, and so on.

Authorization
The act of granting access rights to a user, group of users, system, or process.

B1
A set of G.826 measurements available for the RS-STM-1/Section OC-3/STS-3
layer rates.

B2
A set of G.826 measurements available for the MS-STM-1/Line OC-3/STS-3 layer
rates.

Batch file
A text file containing a series of commands intended to be executed by the
command interface. Batch files in windows are suffixed with .bat or .cmd and can
be edited in a simple word editor.

Backup
Refers to making copy of a dataset such that original dataset can be restored after
a data loss event.

CTP
A Connection Termination Point (CTP) represents a timeslot (or channel) of a
Topological Link. It is also a potential or actual end point of a Cross Connect in a
Network Element. A CTP will always be contained in a PTP, and the CTP will
disappear if the PTP (representing the physical port) is removed. The actual
number and type of CTPs in a PTP can be dynamic. This is called structuring or
channelization.
Ceragon Proprietary and Confidential Page 134 of 145
NetMaster NMS R13C301 Installation Guide

CC
A Cross Connect (CC) represents a connection between CTPs within a Network
Element. A CC can only exist between CTPs with the same Layer Rate. A CC is
transparent to the signal that is transported over it.
Different types of Cross Connects are needed to build different network
topologies. The following Cross Connect types are envisaged:
 Unidirectional, point to point, no protection
 Unidirectional, drop to two or more sinks, no protection
 Unidirectional, point to point, SNC protection
 Bidirectional, point to point, no protection
 Bidirectional, point to point, SNC protection
 Double add-drops and ring interconnects

Customer
A Customer is the client of the Service. Customer specific information such as
name, address, phone, e-mail, etc. is used for identifying and communicating with
the customer. A set of preferred notification methods should be specified (e.g. the
customer would like to be instantly notified by SMS when a service is deferred).
The customer can have several services of different service types. The following
service types are envisaged:
 Connection Service (Leased lines)
 VPN ( VLAN Service)
Customers are created and deleted by the operator of the system .

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 administration levels and associated users.

Database schema
A database user which is the owner of database objects.

Database user
A database user which has some specified access to the database.

Domain
Same as Administrative Domain. An administrative domain is used to group other
resources in NetMaster. An administrative domain can contain any other resource
in the network, including other administrative domains.

Ceragon Proprietary and Confidential Page 135 of 145


NetMaster NMS R13C301 Installation Guide

ELEMENT TRAP RECEIVER LIST FULL


An alarm that is generated by NetMaster to the Active and Historical Alarms table
to indicate that NetMaster has failed to add a trap receiver on an NE due to a full
trap receiver list on the NE.
To resolve an element trap receiver list full situation, do one of the following:
 Delete an entry from the NE's trap receiver list manually using an external
configuration tool
 Change Trap Receiver Strategy for the assigned connection template

EMS
The Element Management System (EMS) represents the hardware and software
components used by the SP or Network Provider to manage one or more Network
Elements ( NEs). The EMS provides management across a subnetwork or a single
NE, typically across a piece, or collection of pieces of equipment from a single
vendor. The EMS performs management functions across the Element
Management Layer ( EML) of the TMN. Some examples of these management
functions include provisioning of NE resources and collection of NE faults.

Equipment
A piece of Equipment represents a manageable physical component of a Network
Element, such as an interface module, a fan module or a power module. The
identity of the equipment does not change during its lifetime.

Equipment holder
An NE can contain different racks that can contain slots that again contain
modules. Many NEs have a flexible configuration, e.g. different module types can
be inserted in a given slot. The Equipment Holder is a general abstraction of a
resource in a Network Element that is capable of holding other resources and it
can represent a Rack, a Sub-Rack, a Shelf, a Slot and a Sub-Slot. Since the
Equipment Holder shall know whether it holds a piece of Equipment (e.g. Module)
or not, it can hold only one piece of Equipment (but it can hold several EHs).The
identity of the Equipment Holder does not change during its lifetime.

Equipment model
The NetMaster equipment model is a simplified representation of the element
based on modeling principles outlined by TMF.

Error
A deviation of a system from normal operation.

Export Database
Pull data out from the database to either a database native format or a common
format.

Ceragon Proprietary and Confidential Page 136 of 145


NetMaster NMS R13C301 Installation Guide

Failover
The capability to switch over automatically to a redundant system upon an
eventual failure.

Fault
The physical cause of a malfunction. Faults manifest themselves as errors.

Fault Management
In network management, the set of functions that detect, isolate, and correct
malfunctions in a telecommunications network, and compensate for
environmental changes. They include:
 Maintaining and examining error logs
 Accepting and acting on error detection notifications
 Tracing and identifying faults
 Carrying out sequences of diagnostics tests
 Correcting faults, reporting error conditions
 Locating and tracing faults by examining and manipulating database
information.

GUI
Graphical User Interface. A general term, describing a program interface that uses
a computer's graphics capabilities to access and control a computer program. A
GUI involves the use of a mouse and keyboard to select objects, including icons,
menus, text boxes, etc. A GUI includes standard formats for representing text and
graphics.

HA
High Availability.

High Availability
A system design and implementation which together ensures a certain absolute
degree of operational continuity.

HTTP LOGON FAILURE


An alarm that is generated by NetMaster to the Active and Historical Alarms table
to indicate that NetMaster has failed to connect to an NE due to wrong HTTP
username/password.

Ceragon Proprietary and Confidential Page 137 of 145


NetMaster NMS R13C301 Installation Guide

To resolve an HTTP logon failure situation, do one of:


 Change username or password on the element using an external configuration
tool
 Change username or password in the assigned connection template for the
element
 Assign another connection template with correct username and password to
the element

Import Database
Put data back into to database. This is done with previously exported data.

Initial primary server


The server which was initially configured as primary server, regardless of its
current role.

Initial standby server


The server which was initially configured as standby server, regardless of its
current role.

Layer rate
The Layer Rate (also referred to as Characteristic Information) is used to identify
the signal type supported by a specific resource.
Examples of Layer Rates are:
 E1
 E3
 E4
 TU-12/VC-12
 TU-3/VC-3
 AU-4/VC-4
 MS STM-0
 MS STM-1
 MS STM-4
 MS STM-16
 RS STM-0
 RS STM-1
 RS STM-4
 RS STM-16
 Digital Signal Rate STM-0
 Digital Signal Rate STM-1
 Digital Signal Rate STM-4

Ceragon Proprietary and Confidential Page 138 of 145


NetMaster NMS R13C301 Installation Guide

 Digital Signal Rate STM-16


 Optical Section
 Physical Optical
 Radio Section
 Physical Radio
 Ethernet
 Fast Ethernet
 Gigabit Ethernet

Line OC-3/STS-3
An ANSI layer rate. The G.826 B2 parity bits can be found in this layer rate.

Link Error measurements


A set of Nera proprietary performance measurements which is mapped to RIU in
NetMaster, representing unswitched bit error counters from the radio link.

LOST CONTACT
An alarm that is generated by NetMaster to the Active and Historical Alarms table
to indicate "Loss of Connectivity" with an NE. Loss of Connectivity state occurs
when no contact has been made with an NE within a configurable poll interval.
Poll interval is configured in the preference menus SNMP Connectivity Polling
and Q1 Polling. For some NE types the poll interval is configured in connection
templates, making it possible to have different poll settings for the different
element types, and even for groups of elements of the same type.

ME
A Managed Element (ME) is an abstract representation of a Network Element.

MS-STM-1
An ETSI layer rate. The G.826 B2 parity bits can be found in this layer rate.

NE
Abbreviation for Network Element. A physical entity in the network with a well-
defined functionality. NEs can be managed (they are then represented by a
Managed Element) or unmanaged. They form the basic infrastructure, i.e. the
hardware and software components of the network.

NE TYPE MISMATCH
An alarm that is generated by NetMaster to the Active and Historical Alarms table
to indicate that NetMaster has detected an NE of unexpected type at a given IP
address.

Ceragon Proprietary and Confidential Page 139 of 145


NetMaster NMS R13C301 Installation Guide

When an element is discovered and set to managed state, NetMaster stores the IP
address and network element type. If for some reason the network element type
changes, NetMaster is no longer able to manage the element correctly.
In this case, NetMaster will do the following:
161 Raise an NE TYPE MISMATCH alarm and clear all other active alarms for
this element.
162 Remove all child nodes from the element model in the Geographical Tree
or Logical Tree views.
To resolve an NE Type Mismatch situation:
163 Add a network element of correct type at the given IP address.
164 Delete the NE from managed state, and also delete from the Unmanaged
Elements table.
165 If the new element type is supported by NetMaster, discover and manage
the element again

Nera Configuration Manager


An element configuration tool for older Nera NE types, also known as New-NMS.

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.

NetMaster server
The NetMaster service instance which is monitored by the NetMaster Server
Monitor.

Network Element
A physical entity in the network with a well-defined functionality. Network
Elements (NEs) can be managed (they are then represented by a Managed
Element) or unmanaged.
They form the basic infrastructure, i.e. the hardware and software components of
the network.

Network manager
A system for controlling and monitoring a network of NEs. NetMaster is a software
package providing a typical network manager system.

Network Operator
An organization that operates a communications network, network or data
services capability, acting basically as a wholesaler. A network operator is a
service provider. A service provider may provide the network operator role or
may subcontract this role.
Ceragon Proprietary and Confidential Page 140 of 145
NetMaster NMS R13C301 Installation Guide

Node
Any object that can be found in a topological map, including both domains and
NEs.

PDH Parity measurements


A set of Nera proprietary performance measurements in the PDH frame which can
be found under the Physical Radio layer rate in NetMaster.

Performance Management
Performance Management provides functions to evaluate and report upon the
behavior of telecommunication equipment and the effectiveness of the network or
network element. Its role is to gather and analyze statistical data for the purpose
of monitoring and correcting the behavior and effectiveness of the network, NEs
or other equipment and to aid in planning, provisioning, maintenance and the
measurement of quality.

Primary server
The server which is currently in production or in operational mode.

PTP
A Physical Termination Point (PTP) is an actual or potential end point of a
Topological (physical) Link. Basically a representation of a physical port of a
Network Element, e.g. an E1 port, an STM-N radio port, etc.

PTP and CTP channelization


Channelization (or structuring) of a PTP or CTP describes how the aggregate
signal is split into tributaries or ( timeslots). It can be seen as a representation of
the multiplexing structure of a port or termination point. The channelization of a
PTP or CTP is given by the number of CTPs it contains. Whereas a PTP can never
be included in a connection, a CTP can only be included in a connection if it is not
channelized ( i.e.: it is not terminated and it does not contain other CTPs). In SDH
and SONET there can be two levels of CTPs above the PTP.

Reconcile Alarms
Local alarms are aligned with NE alarms.

Recover Database
A process of regaining a lost state.

RECONCILED ACTIVE ALARMS


An alarm that is generated by NetMaster to the Historical Alarms table for
Evolution series NE in some special cases.

Ceragon Proprietary and Confidential Page 141 of 145


NetMaster NMS R13C301 Installation Guide

Whenever NetMaster discovers that traps are lost from a NE, NetMaster uses
polling to need to reconcile alarms with the NE. For more details, see how to
configure polling and traps in NetMaster.
For Evolution series NEs, NetMaster offers extended functionality for alarm
reconcile. NetMaster has two policies for synchronizing alarm reading for this NE
type:
Reconcile fault log:
NetMaster will reconcile with the Evolution NE’s fault log whenever possible. This
means that alarm events can be retrieved from the NE, even if the NetMaster
server was disconnected from the NE when the alarm event occurred. When
connection to the element is restored the NetMaster server will read the missing
alarm events from the NE’s fault log.
As long as NetMaster is able to reconcile fault log, NetMaster will have a complete
list of alarms that has appeared in the Evolution NEs.

Reconcile active alarms:


The NetMaster server will reconcile with the NE’s active alarm status in the
following situations:
-when NetMaster server is restarted
-when NE is set in managed state
-when NE is restarted
-if number of lost alarms in the NE’s fault log exceeds 200
-If reading of NE’s fault log fails
When active alarms are reconciled, NetMaster might lose some alarms from the
Evolution NE's fault log. This is indicated by inserting an alarm with alarm text
"RECONCILED ACTIVE ALARMS" in the Historical Alarms view.

Regular Expression Syntax


A regular expression is a special sequence of characters that helps you match or
find other strings or sets of strings, using a specialized syntax held in a pattern.
They can be used to search, edit, or manipulate text and data. The following is an
overview of regular expressions symbols and metacharacters. For a complete
tutorial about regular expressions, visit the following web page www.regular-
expressions.info/tutorial.html.
Common matching symbols:
Regular Expression Description
. Matches any sign except newline
^regex regex must match at the beginning of the line
regex$ Finds regex must match at the end of the line
[abc] Matches any single character in brackets (a or b or c)
[abc][xy] Matches a or b or c followed by either x or y
[^abc] Matches any single character not in brackets

Ceragon Proprietary and Confidential Page 142 of 145


NetMaster NMS R13C301 Installation Guide

Regular Expression Description


[a-h1-8] Ranges, letter between a and h and digits from 1 to 8
a|b Matches either a or b
ab Matches a directly followed by b
^ Matches beginning of line
$ Matches end of line

Metacharacters:
Regular Expression Description
\d A digit, short for [0-9]
\D A non-digit, short for [^0-9]
\s A whitespace character, short for [ \t\n\x0b\r\f]
\S A non-whitespace character, for short for [^\s]
\w A word character, short for [a-zA-Z_0-9]
\W A non-word character [^\w]

Quantifiers:
Meta Character Description Example
regex* Matches 0 or more occurrences of X* - Finds 0 or several letter X,
preceding expression. It is short for {0,} .* - any character sequence
regex+ Matches 1 or more of the previous X+ - Finds one or several letter X
expression. It is short for {1,}
regex? Matches 0 or 1 occurrence of preceding X? - Finds one or zero letter X
expression. It is short for {0,1}
regex{n} Matches exactly n number of occurrences \d{3} - Three digits,
of preceding expression. .{10} - any character sequence of length
10
regex{n,} Matches n or more occurrences of \d{4,} - \d must occur at least four times or
preceding expression. more
regex{n,m} Matches at least n and at most m \d{1,4} - \d must occur at least once and at
occurrences of preceding expression. a maximum of four
*? ? after a qualifier makes it a "reluctant Given input "aXaaXaaaXaaaa" :
quantifier", it tries to find the smallest X.*X gives "XaaXaaaX"
match.
X.*?X gives "XaaX"

Ceragon Proprietary and Confidential Page 143 of 145


NetMaster NMS R13C301 Installation Guide

Restore Database
Is a process of regaining a previous state.

RMAN
Is the Oracle Recovery Manager tool and is used for Oracle backup administration.

Root-cause problem
The fundamental cause(s) that, if corrected, will prevent recurrence of an event or
alarm.

RS-STM-1
An ETSI layer rate. The G.826 B1 parity bits can be found in this layer rate.

Search range
An IP search range is a sequence of IP addresses which will be used when
discovering (looking for) NEs. A search range consist of a lower boundary, and a
high boundary, and the NetMaster server will sequentially send a request to each
of the IP addresses within this range (including both lower and higher
boundaries) to see if any NEs respond.

Section OC-3/STS-3
An ANSI layer rate. The G.826 B1 parity bits can be found in this layer rate.

SNMP
Simple Network Management Protocol. A communications protocol used in the
monitoring and management of communications devices and services. SNMP
utilises three basic request primitives: Set, Get and Get Next for configuration and
performance information, and one asynchronous notification: Trap for alarm and
status information.

Standby server
A mirror of a primary server which is constantly updated to keep data in synch.
This is used for redundancy in a High Availability configuration.

Station
A Station represents a physical location where Network Elements and other
equipment is installed. A Station is used to provide location information such as
address, coordinates etc. that is specific for the location.

Subnet mask
An IP network can be split into a series of subnets using Subnet masks. A Subnet
mask distinguishes the network ID from the host ID in an IP address, and is used
to determine what subnet an IP address belongs to.
Ceragon Proprietary and Confidential Page 144 of 145
NetMaster NMS R13C301 Installation Guide

SNC
A Subnetwork Connection (SNC) relates end-point CTPs. A SNC provides a
transparent end-to-end connection through or within a Subnetwork.

Subnetwork
A Subnetwork is an abstraction provided by the EMS to the NMS which describes
the potential for Subnetwork Connections (SNC).

Switchover
Is a process where the server running as primary switches role to standby and the
standby server switches role to primary server without any loss of data.

Topological Link
A Topological Link (TL) in NetMaster represents a uniform group of physical
connections between two Managed Elements. In NetMaster, the two connections
are referred to as the aEnd and the zEnd of the TL.
The group will be uniform in the sense that all connections in the group will have
the same layer rate, i.e. radio, ethernet, e1. A connection is mapped to a TL as a
pair of termination points (TPs), one from aEnd and one from zEnd. Alarms at TPs
can be mapped and visualized on a TL.

TP
A Termination Point (TP) can be either a Physical Termination Point (a plug on
the ME) or a Connection Termination Point (internal termination point).

Ceragon Proprietary and Confidential Page 145 of 145

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy