NetMaster Installation Guide
NetMaster Installation Guide
NetMaster Installation Guide
Installation Guide
November 2013
Release: R13C01
Rev A
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.
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
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
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
all optional features installed, the NetMaster system provides the operator with an
advanced and sophisticated network management system that will highly increase
the efficiency of operations and maintenance in the network.
For easy integration to external higher-level management systems, a Northbound
SNMP interface can be provided.
Installation Guide
The NetMaster NMS Installation Guide is the printed version of installation section
of the online help system for the NetMaster network management system. The
installation guide can provide you with help about how to install and how to
configure the application. For detailed information regarding how to use
NetMaster, including system management information, please see the NetMaster
NMS User Guide.
More information
If you cannot find the answer to your question in the installation manual, contact
your responsible support person.
2. NetMaster Installation
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.
Server NetMaster Client, NetMaster Server, SNMP Agent and System Manager.
System Manager System Manager only. Intended for stand-alone database server installation.
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.
If you accept the agreement, select the Accept option and then click Next to
continue.
Choose Install Set step. Note that the NetMaster Server install sets include Server,
System Manager, Client and Northbound SNMP Agent.
\
Click Next to continue.
Choose Install Set step - Custom. This step is only displayed if the "custom"
install set is selected in the previous step.
In this step you can select each component individually. See the Description field
for information about the selected component.
Installing step
Watch the product features being presented during the installation progress.
Click Done to finish the wizard. The installation wizard configures the system
when completing the wizard.
If included in the installation set, System Manager can be opened at the end of
installation:
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.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:
The Introduction step displays some general information about the installation
process
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.
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.
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
System Manager Configuration and maintenance tool for NetMaster Server. System Manager must be
installed on both the NetMaster Server and the database server.
System Manager System Manager only, intended for stand-alone database server installation.
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.
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
The NetMaster Client can now be started by running the NetMaster executable.
See the chapter on NetMaster GUI Client for more details.
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]
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
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.
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.2 Oracle
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.
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.
End of Installation. The installation is completed. Click Exit to close the installer,
and confirm in the message box that pops up.
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.
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.
End of Installation. The installation is completed. Press Exit to close the installer,
and confirm in the message box that pops up.
System Class. Select according to the class of system hosting oracle database.
Install Type. Select Advanced Install if you want additional configuration during
install.
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.
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.
Summary. Displays a summary of the selections made above. Please verify settings
and Database information, including SID
Click OK to continue.
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.
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.
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.3 PostgreSQL
1. Introduction screen
Introduction message.
2. Installation Directory
Select the installation directory. You can change the directory by selecting Browse
to pick the new directory.
3. Data Directory
Select the directory under which data will be stored. Note that the 'Data Directory'
option may only be installed on an NTFS partition. If you wish to install the data
directory on any other partition type, you will need to run initdb.exe manually
after installation.
4. Password
Enter and confirm the password to be used for the superuser account (postgres)
in the database cluster. This password is also used for the service account and
must match the current password if the account already exists. You can change the
superuser password independently of the service account password at any time
following the installation.
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
5. Port
Select the port that the server will listen on. You may specify a non-default port
number to run the server on (If you change the default port, please make a note of
it, as you will need it while installing the NetMaster server)
If you plan to run NetMaster server and the PostgreSQL server on separate
machines, you will also need to enable access in the host based authentication
configuration (pg_hba.conf) to allow remote users to connect to the server. This is
covered in the chapter on PostgreSQL Post Installation.
6. Advanced Options
Choose the locale that the cluster will be initialized with. By default the locale is
selected as "default locale", from the drop down select "C".
This will initialize the database with ISO C locale and UTF-8 encoding.
7. Ready to install
8. Installing
A progress bar is shown during the installation.
On some versions of Windows (notably Windows XP before Service Pack 2 and
Windows 2003 before Service Pack 1 - see Microsoft Knowledge Base article
Q818858) a Command Prompt window will appear during the "Initializing
database cluster" step. Don't close this window - it will automatically close once
the operation is complete.
9. Finished
Unselect the option “Launch Stack Builder at exit” .Installation is complete. You
can now go ahead and test your installation.
Click Finish.
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.
The table below contains required minimum values for running NetMaster with
PostgreSQL:
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.
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.
2+2 HA Configuration
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.
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.
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.
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.
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. 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.
5. Enter the start date and time and how often it should run each day.
6. Click Next.
Create a basic task – action
2.5.6.2 Concepts
Subsystem
A subsystem consists of a host running NetMaster server, and a host running the
database.
Active subsystem
The subsystem that is used for daily tasks. All updates (manage element, define
services, manage users, etc.) shall be done on the active subsystem. It is important
that all NetMaster users are aware of which subsystem is active.
Standby subsystem
The redundant subsystem that is kept synchronized with the active subsystem, on
a scheduled basis, usually daily. This subsystem should be used by NetMaster
clients only for read operations. Please note: There is nothing that prevents users
from updating the standby subsystem, but these updates will be lost upon
synchronization.
Synchronization
The process of backing up the active system, transferring the backup to the
standby system, and then restoring the standby system.
2.5.6.3 Functionality
The log will show what decisions/actions were taken, and report on lost contact,
or other errors.
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)
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).
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
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
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>)
)
)
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.
If the system returns the following, see “Appendix: Problems & Solutions,
Cannot find samba net program” to fix the problem.
If the system returns the following, correct the admin user and password:
If system returns the following, start the netlogon service on the nm host.
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/
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
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
my-ip
The my-ip file may be needed in case a db host has multiple ip addresses. See
Configure the IP address.
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.
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.
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
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
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.
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
#!/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
/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 ""
# start sshd
/etc/init.d/sshd start
...
NET=/usr/sfw/bin/net
#or:
#NET=/usr/sfw/sbin/net
Problem: When running the net program, the output starts with message similar
to this:
[2013/05/15 10:15:28, 0] param/params.c:(536)
params.c:OpenConfFile() - Unable to open configuration file
"/etc/sfw/smb.conf":
No such file or directory
Solution:
User : root
Check for the existence of the file /etc/sfw/smb.conf on db1 and db2 hosts.
If the file 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
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>
3. Appendix
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.
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.
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:
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:
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.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.
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.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.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).
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 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.
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.
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.
Import Database
Put data back into to database. This is done with previously exported data.
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
Line OC-3/STS-3
An ANSI layer rate. The G.826 B2 parity bits can be found in this layer rate.
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.
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
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.
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.
Reconcile Alarms
Local alarms are aligned with NE alarms.
Recover Database
A process of regaining a lost state.
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.
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"
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).
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: