HighCapRadioNMS Installation Guide - N7.0.0.1.0

HighCapNMS
N7.0
Installation and Configuration Guide
Rev C.01
May 2013

HighCapNMS
N7.0 Installation and Configuration Guide

HighCapRadio Proprietary and Confidential Page 2 of 85
Table of Contents
1. HighCapNMS System Requirements ............................................................... 5
1.1 Minimum Software Requirements .................................................................................. 5
1.1.1 FTP Server ..................................................................................................................... 5
1.1.2 My SQL Database .......................................................................................................... 5
1.1.3 Supported Operating Systems ....................................................................................... 5
1.1.4 Supported Browsers ....................................................................................................... 5
1.2 Minimum Hardware Requirements ................................................................................ 6
1.3 Locating the HighCapNMS Server in the Network ......................................................... 6
2. Initial Installation Procedure ............................................................................ 7
2.1 Installation Notes ............................................................................................................ 7
2.2 Installation Order ............................................................................................................ 7
2.3 MySQL installation ......................................................................................................... 7
2.3.1 Windows ......................................................................................................................... 7
2.3.2 Unix ................................................................................................................................ 7
2.4 FTP Server Installation................................................................................................... 8
2.5 VarioManager Installation .............................................................................................. 8
2.5.1 VarioManager Minimum System Requirements ............................................................ 8
2.5.2 Installation Procedure .................................................................................................... 9
2.5.3 Logging in to VarioManager ........................................................................................... 9
2.5.4 Setting Permissions ..................................................................................................... 10
2.5.5 Configure TFTP Settings.............................................................................................. 11
2.6 HighCapNMS Server Installation ................................................................................. 11
2.6.1 Installing on Windows .................................................................................................. 11
2.6.2 Installing on Unix .......................................................................................................... 12
2.6.3 HTTP Proxy Installation and Configuration .................................................................. 12
2.6.3.1 HTTP proxy installation on Microsoft Windows systems ............................. 12
2.6.3.2 HTTP Proxy Installation on Sun Solaris Systems ....................................... 15
2.7 Client-Browser Configuration ....................................................................................... 19
3. HighCapNMS Upgrade Procedure ................................................................. 22
3.1 Limitations and Warnings ............................................................................................. 22
3.1.1 MySQL Upgrade to Version 5.1 ................................................................................... 22
3.1.2 Database Persistence .................................................................................................. 22
3.1.2.1 Restoring Previous Database Data ............................................................. 22
3.1.2.2 Restoring Topology Data ............................................................................. 23
3.1.2.3 Required Disk Space for Upgrade and Restoring ....................................... 23
3.1.2.4 Time Required for Upgrade and Restoring ................................................. 23
3.1.2.5 User Directories ........................................................................................... 24
3.2 Upgrading HighCapNMS on Windows Servers ........................................................... 24
3.2.1 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N7.0 .......................................................... 24
3.2.2 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N7.0 and Restoring Old Data ................... 26
3.2.2.1 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N6.6.1.5.1 with Data Restoration
..................................................................................................................... 26
3.2.2.2 Upgrading from N6.6.1.5.1 to N7.0 with Data Restoration .......................... 27
HighCapNMS

3.2.3 Upgrading from N6.6.1.x.x to N7.0 and Restoring Old Data........................................ 28
3.2.3.1 Upgrading from N6.6.1.x.x to N6.6.1.5.1 with Data Restoration ................. 28
3.2.3.2 Upgrading from N6.6.1.5.1 to N7.0. with Data Restoration ......................... 29
3.3 Upgrading HighCapNMS on Solaris Servers ............................................................... 29
3.3.1 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N7.0 .......................................................... 29
3.3.2 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N7.0 and Restoring Old Data ................... 31
3.3.2.1 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N6.6.1.5.1 with Data Restoration
..................................................................................................................... 31
3.3.3 Upgrading from N6.6.1.x.x to N7.0 and Restoring Old Data........................................ 34
3.3.3.1 Upgrading from N6.6.1.x.x to N6.6.1.5.1 with Data Restoration ................. 34
3.4 Upgrading servers in Redundancy Mode ..................................................................... 35
3.4.1 Prerequisites ................................................................................................................ 35
3.4.2 Upgrading the Main and Standby Servers ................................................................... 36
3.5 Downgrading to HighCapNMS N6.6.0.1.2 ................................................................... 37
3.5.1 Downgrading to HighCapNMS N6.6.0.1.2 on Windows Servers ................................. 37
3.5.2 Downgrading to HighCapNMS N6.6.0.1.2 on Solaris servers ..................................... 38
4. Testing Server Installation ............................................................................. 40
4.1 Testing a Standalone Server Installation ..................................................................... 40
4.2 Testing Redundant Servers ......................................................................................... 42
5. Configuring your System ............................................................................... 43
5.1 Configuring the FTP Server ......................................................................................... 43
5.2 HighCapNMS Server Configuration ............................................................................. 43
5.2.1 General Settings .......................................................................................................... 44
5.2.2 Polling Settings ............................................................................................................ 45
5.2.3 File Transfer Settings ................................................................................................... 46
5.2.4 Security Settings .......................................................................................................... 47
5.2.5 Redundancy Settings ................................................................................................... 49
5.2.6 Alarms Settings ............................................................................................................ 51
5.2.7 Advanced Settings ....................................................................................................... 52
5.3 HighCapNMS Client Configuration .............................................................................. 53
5.3.2 Remote Hosts Settings ................................................................................................ 54
5.4 Client Browser Configuration ....................................................................................... 55
5.5 Trap Forwarding ........................................................................................................... 56
5.5.2 OSS Settings ................................................................................................................ 59
5.6 DCN Sizing ................................................................................................................... 60
5.6.1 HighCapNMS Server - HighCapNMS Client Client ...................................................... 60
5.6.2 HighCapNMS Server - Network Element Network ...................................................... 61
5.6.3 Local Connection to the Network Element ................................................................... 61
5.6.4 HighCapNMS Northbound Interface ............................................................................ 61
5.6.5 Redundant Server Solution - HighCapNMS ................................................................ 61
HighCapNMS

5.7 Ethernet Services Pre-Configuration ........................................................................... 62
5.7.1 Pre-Configuration Overview ......................................................................................... 62
5.7.1.1 Concepts and Acronyms ............................................................................. 62
5.7.1.2 Acronyms ..................................................................................................... 63
5.7.2 IP Table Configuration ................................................................................................. 63
5.7.2.1 Ethernet Peer Ports Configuration ............................................................... 64
5.7.2.2 Exceptions ................................................................................................... 64
5.7.2.3 Examples ..................................................................................................... 64
5.7.3 Peer Port Configuration................................................................................................ 66
5.7.3.1 Peer IP Address ........................................................................................... 66
5.7.3.2 Peer Slot Number ........................................................................................ 67
5.7.3.3 Peer Port Number ........................................................................................ 67
5.7.3.4 Exceptions ................................................................................................... 68
5.7.3.5 Examples ..................................................................................................... 69
5.7.4 Ethernet Ports Table Configuration .............................................................................. 70
5.7.4.1 Port Admin ................................................................................................... 70
5.7.4.2 Port Type ..................................................................................................... 71
5.7.4.3 Port Service Type ........................................................................................ 71
6. HighCapNMS Network Support ..................................................................... 73
6.1 Supported Protocols ..................................................................................................... 73
6.2 Port List ........................................................................................................................ 73
6.2.1 Ports Used for Sending from HighCapNMS Server ..................................................... 73
6.2.2 Ports Used for Receiving to HighCapNMS Server ...................................................... 74
6.2.3 Ports Used for Sending from VarioManager ................................................................ 77
6.2.4 Ports Used for Receiving to VarioManager.................................................................. 77
6.2.5 Ports Used for Sending from the Web Based EMS ..................................................... 77
6.2.6 Ports Used for Receiving to the Web Based EMS ....................................................... 77
7. HighCapNMS License Information ................................................................ 78
7.1 Introduction .................................................................................................................. 78
7.2 License Requirements ................................................................................................. 78
7.3 License Components ................................................................................................... 79
7.3.1 Redundancy Server Support ........................................................................................ 79
7.3.2 TDM Trail License Requirements ................................................................................ 79
7.3.3 Ethernet Services License Requirements .................................................................... 79
7.4 Licensing MySQL ......................................................................................................... 80
7.5 Temporary Demo License ............................................................................................ 80
7.6 Obtaining a Permanent License ................................................................................... 80
7.7 License Configuration Recommendations ................................................................... 81
7.8 License Configuration Examples ................................................................................. 81
8. Hardware Capacity Recommendations ......................................................... 83
8.1 Unix Server Capacity Examples .................................................................................. 83
8.2 Windows Server Capacity Recommendations ............................................................. 84
9. Compatibility Matrix ....................................................................................... 85

HighCapNMS

1. HighCapNMS System Requirements
1.1 Minimum Software Requirements
1.1.1 FTP Server
HighCapNMS uses of external FTP server application which is running on the
server.
Solaris and HP servers use the UNIX operating system's built-in FTP server.
Windows servers require an external FTP server: HighCapNMS is configured
to work with FileZilla FTP server.
The FileZilla FTP server must be installed before installing HighCapNMS.
The NMS server is configured to find the FTP server under its default
location: C:\ProgramFiles\FileZilla Server\.
Once HighCapNMS is installed it is optional to install different FTP server.
1.1.2 My SQL Database
HighCapNMS uses internal MySQL SW database. A MySQL license should be
purchased for each server running HighCapNMS.
Marketing Model Item Description Part Number
MYSQL-LICENSE MySQL software License for Windows/Unix platform. SL-0003-X
1.1.3 Supported Operating Systems
Server & client OS support
Windows XP
Windows Server 2003 (32 & 64 bit)
Windows Server 2008 (32 & 64 bit)
Windows Server 2008 R2 (32 & 64 bit)
Windows Server 2008 64 bit on a VMware server
Windows 7 (32 & 64 bit)
Solaris 10, Oracle (Sun SPARC processor)
1.1.4 Supported Browsers
IE 6, 7, 8, 9
Firefox -
Mozilla 5.0
HighCapNMS

1.2 Minimum Hardware Requirements
Component Windows requirements Unix requirements
Hardware type Any type T2/T3
Processor Core 2, 2.0 GHz Sun SPARC
Memory (RAM) 2 GB 8 GB
Available drive space 120 GB 73 GB x 2
Operating system Windows server 2003 and 2008 (32 / 64 bit/
XP / 7)
Solaris 10
Ethernet ports 1 1

1.3 Locating the HighCapNMS Server in the Network
Since the HighCapNMS server contains sensitive network information, it is
highly recommended to locate the HighCapNMS server in the same securer
network area as the network elements, i.e., behind a secured DMZ.
Communications between the HighCapNMS server and XPAND IP+ network
elements take place through a proprietary protocol that is not trivial to
understand. This communication does not make use of identification
credentials. However, locating the HighCapNMS server as recommended
above will greatly diminish the risk of unauthorized users gaining access to
this communication channel.
HighCapNMS

2. Initial Installation Procedure
2.1 Installation Notes
When installing HighCapNMS on a 32 bit operating system, the
HighCapNMS directory should be located under: \Program Files (x86)\
The installer and the user shouldboth have administrator permissions.
2.2 Installation Order
The initial installation must be installed in the following order:
1 Install MySQL
2 Install FTP server (Windows OS)
3 Install VarioManager
4 Install HighCapNMS Server
5 Request a permanent license.
2.3 MySQL installation
HighCapNMS cannot operate without its internal SQL database (MySQL DB).
The MySQL database is provided as part of the basic HighCapNMS installation
but requires its own license, which needs to be purchased separately.
2.3.1 Windows
To install MySQL on a Unix server:
1 Run the MySQL installer that is supplied with the installation kit.
Note: If OS is Windows 2008 / 7 ensure that MySQL is registered
in the environmental variables under Control Panel >
System > Advanced system settings > Environment
Variables
2 Check the PATH variable under System variables to see it includes the path
to: C:\mysql and C:\mysql\bin. If it is missing add it manually.
3 Restart the server.
2.3.2 Unix
To install MySQL on a Unix server:
1 Uninstall any previous versions of MySQL.
2 Open the terminal and run these commands:
ps ef | grep i mysql (Searches for MySQL processes)
pkill -9 mysql (Stops MySQL processes)
ps ef | grep i mysql
3 Change to the mysql directory and verify that there is only one line in
output.
HighCapNMS

cd /opt/mysql
rm r *
4 Execute the MySQL installation file to install MySQL.
chmod 775 <Mysql installation file>
./< Mysql installation file >
Note: Do not change the default installation location (Windows:
c:\mysql, UNIX: /opt/mysql).
2.4 FTP Server Installation
HighCapNMS NMS uses an FTP server to enable:
Software file downloads
Network element configuration archive backup and restore
On Windows servers, you must install the FileZilla FTP server before installing
HighCapNMS.
Ensure that FileZilla is installed in C:\Program Files\FileZilla, as FileZilla will
default to C:\Program Files (x86) on a 64-bit OS.
2.5 VarioManager Installation
2.5.1 VarioManager Minimum System Requirements
For Windows:
Specification Minimum (less than 50 elements)
Hardware Type Any type
Processor Core 2, 2.0 GHz
Memory (RAM) 2 GB
Available Drive Space 120 GB
Operating System Windows 2003 Server/XP
Display Monitor 1280x1024 True Color
Ethernet Ports 1
For UNIX:
Specification Minimum (less than 50 elements)
Hardware Type T2/T3
Memory (RAM) 8 GB
Available Drive Space 73 GB x 2
Operating System Solaris 10
Display Monitor 1280x1024 True Color
Ethernet Ports 1
HighCapNMS

2.5.2 Installation Procedure
Note: For Windows platforms, right click the installer file and
select Run as Administrator.
To install VarioManager as a standalone platform:
1 Run the VarioManager installation program.
2 Click Next to open the License Agreement window.
3 Click I accept and Next to open the NMS Integration window.
4 Select StandAlone and click Next to open the Choose Install Folder
window.
5 Click Choose to select the directory in which you want to install the
VarioManager software.
To restore the system-selected directory, click Restore Default
Folder.
6 Click Next.
In Windows, restart the computer after the installation is complete.
If a message appears informing you that a previous version of
VarioManager will be uninstalled, click Continue.
2.5.3 Logging in to VarioManager
To log in to VarioManager:
1 Ensure that you have Administrator privileges on the PC where you have
installed VarioManager.
i In the Control Panel, double-click Users and Passwords.
ii Click Add.
iii Click Browse, and select the user from the list.
iv Click Next.
v Select Other and Administrators.
vi Click Finish.
2 Select Start > Programs > VarioManager.

3 Enter the relevant information in the fields.
HighCapNMS

The default Administrator login is:
User Name: admin
Password: admin
The default Viewer login is:
User Name: viewer
Password: viewer
4 Select Save Password if you want VarioManager to remember the user
name and password you entered.
5 Click OK.
2.5.4 Setting Permissions
When a user performs an operation not related to a specific network element
(such as changing the security configuration), access permissions will be
calculated by the Default Access line (which contains the Subnet IP and Mask
equal to 0.0.0.0). If a Default Access line does not exist for a user, the user will
not be able to access general network features.
To set VarioManager user permissions:
1 In the main window, right click Users, and select Add User, or right click
an existing user and select Edit User.

2 For a new user, enter the new users name and password in the fields at
the top of the window.
3 In the Access by Subnet area, assign the user a group with the necessary
privileges for each subnet. For example, you can give the user
Administrator rights on one subnet and Observer rights on another.
4 Click OK.
Notes:
You cannot enter the same subnet twice for the same user.
If none of the subnets you entered match an IP the user tries to connect to,
the user will be denied access to that IP.
HighCapNMS

If more than one subnet matches an IP the user tries to connect to, the
group that belongs to the subnet that matches the IP the closest will be
used for the IP access.
For example, you created the user Joe with the following rights:
172.24.0.0 : Observer, and 172.24.30.0 : Administrator. If Joe requests
access to 172.24.30.5, he will be granted Administrator rights for that
IP.
Even though both subnets you assigned to Joe match the IP he
requested, the subnet 172.24.30.0 is closer to the IP than the other one.
To obtain default Observer rights for IP addresses that do not match
any of the subnets in the list, you need to assign the subnet 0.0.0.0 :
Observer to the user, and the subnet mask must also be 0.0.0.0.
2.5.5 Configure TFTP Settings
Make sure to configure the TFTP server address and the full TFTP files
directory path with the same settings as for HighCapNMS.
To configure VarioManager TFTP settings:
1 Open VarioManager Configuration.
2 Select File Transfer.
3 In the TFTP Server Address field, enter the IP address of your server.
4 In the TFTP Files Location field, specify the directory in which the network
element software files are located.
5 In the Use Internal TFTP Server field, select False, since HighCapNMS uses
its own TFTP server.
6 Click Apply.
2.6 HighCapNMS Server Installation
In order to be protected from external security attacks, it is recommended to
run the HighCapNMS server and client with an operating system user that
does not have administrative privileges, but only privileges to read and write
to the HighCapNMS installation directory on the file system.
2.6.1 Installing on Windows
To install HighCapNMS on a Windows server:
1 Install MySQL.
2 Install FileZilla Server
3 Install VarioManager EMS.
4 In Windows 2008 / 7 set the MySQL and HighCapNMS installation files to
XP compatibility mode.
i Right click the installation file.
ii Choose Properties > Compatibility > Compatibility mode.
iii Select Windows XP
5 Turn off User Account Control.
Note: HighCapNMS does not support Vista , nor Vista's User
Access Control (UAC). If the server is installed on Vista, open
HighCapNMS

the Control Panel, double-click User Accounts, select Turn
User Account Control On or Off, and make sure that UAC is
not selected.
6 Run the HighCapNMS installation.
7 Restart the computer before running HighCapNMS and HighCapNMS Client
configuration utilities.
2.6.2 Installing on Unix
To install HighCapNMS on a Unix server:
1 Execute and run the HighCapNMS installation file:
chmod 775 <HighCapNMS installation file>
./< HighCapNMS installation file >
2 Click Next to accept the default installation settings.
3 In the Choose HighCapNMS Features window, make sure that Server is the
selected application.
2.6.3 HTTP Proxy Installation and Configuration
2.6.3.1 HTTP proxy installation on Microsoft Windows systems
Buy and download Sun Java System Web Proxy Server 4.0.8 from the following
web site:
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-
Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJPrxySrv-4.0.8-
OTH-G-F@CDS-CDS_SMI
1 Unzip the sun-web-proxy-server-4.0.8-win.zip file.
2 Run setup.exe to install the web proxy.
3 Start the server by running <installation path>\proxy-admserv\startsvr.
4 Access the proxy admin server via the following URL: http://<machine
name>:8082.
5 In the web proxy admin go to Servers -> Manage Servers (the default
opening location), and click the server1 instance.
HighCapNMS


6 In Preferences -> Start/Stop Server (the default opening location), click
On.
The server can also be started by running:
<installation path>\proxy-server1 \startsvr
HighCapNMS


7 Make sure the server is running (via the proxy-admin, as in the example
above, or via the computer services list).
8 Go to Routing -> Enable/Disable Proxying, select the Enable Proxying
of this Resource option, and click OK.
HighCapNMS


2.6.3.2 HTTP Proxy Installation on Sun Solaris Systems
Buy and download Sun Java System Web Proxy Server 4.0.8 from the following
web site:
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-
Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJPrxySrv-4.0.8-
OTH-G-F@CDS-CDS_SMI
1 Put the downloaded file in the / folder.
2 Open terminal and run "cd /".
3 Run "gzip -d sun-web-proxy-server-4.0.8-sparc.tar.gz".
4 Run "tar -xvf sun-web-proxy-server-4.0.8-sparc.tar".
5 Run "chmod 775 setup".
6 Run "./setup".
7 In the following window make sure that "startup on boot" is checked.
HighCapNMS


8 Start the server by running "/opt/sun/proxyserver40/proxy-
admserv/start".
9 Run "/usr/sfw/bin/mozilla"
10 Access the proxy admin server via the following URL: http://<machine
name>:8081.
11 In the web proxy admin go to Servers -> Manage Servers (the default
opening location), and click the server1 instance.
HighCapNMS


12 In Preferences -> Start/Stop Server (the default opening location), click
On.
HighCapNMS


13 Make sure the server is running (via the proxy-admin, as in the example
above, or via the computer services list).
14 Go to Routing -> Enable/Disable Proxying, select the Enable Proxying
of this Resource option, and click OK.
HighCapNMS


2.7 Client-Browser Configuration
For each browser that will access the web interface, configure the following:
1 Open a browser window.
2 In the Tools menu, select Internet Options.
3 Select the Connections tab.
4 Click LAN Settings.
HighCapNMS


5 In the Proxy Server area, select Use a proxy server for your LAN.
6 In the address area, specify the address of the machine on which the web
proxy server is installed.
7 For Port, enter 8080 (or a different port number if configured otherwise in
the web proxy server).
HighCapNMS


HighCapNMS

3. HighCapNMS Upgrade Procedure
When upgrading from version 6.6.1.3.1 or higher no need to upprade
MySQL.
Stop the NMS process, run the new version installer, and restart the NMS
process.
When upgrading from versions older than 6.6.1.3.1 follow the
instructions in the appropriate section below.
3.1 Limitations and Warnings
3.1.1 MySQL Upgrade to Version 5.1
WARNING: MySQL version 4.17 had been declared obsolete and is no
longer supported by HighCapRadio.
From HighCapNMS version N6.6.1, the HighCapNMS database has been
upgraded with new tables that are optimized to work with MySQL 5.1.
Upgrading to N6.6.1 and higher will force an upgrade from MySQL version
4.17 to MySQL version 5.1.
MySQL licenses are owned by HighCapRadio. Therefore HighCapRadio
requires users to report details for every server that has been upgraded to
MySQL 5.1:
Customer details: Final customer, Integrator, Region, Country.
Server details: Operating System, Serial Number.
License details: Host ID, Maximum NEs in license.
General details: Installed by, Installation Date, Notes (if any).
3.1.2 Database Persistence
Upgrading MySQL will overwrite your current data with a new database.
When the HighCapNMS upgrade is completed, the system will poll new data
from the network elements.
Before starting the upgrade procedure, it is therefore recommended to
generate reports for all history PMs/Alarms that you wish to save. These
reports can be exported to CSV format to be opened in MS-Excel.
3.1.2.1 Restoring Previous Database Data
Data from HighCapNMS version N6.7.x.x.x is kept by default during upgrade
and no need any manual conversion or restore.
Data from HighCapNMS versions N6.6.0.0.2 / N6.6.0.1.2 / N6.6.1.x.x can be
restored by upgrading first to N6.6.1.5.1 and then to N7.0.
However, due to the complexity of the restoration procedure, HighCapRadio
strongly recommends to store previous data as described above and start with
a clean database with HighCapNMS version N7.0 and MySQL 5.1.
HighCapNMS

Customers planning to maintain old data should contact HighCapRadio for
support.
Upgrading from older versions than N6.6.0.0.2 should be treated as initial
installation.
3.1.2.2 Restoring Topology Data
Before performing the HighCapNMS upgrade, customers should export the
existing system topology and import the topology to the new version.
Do not add or remove elements to the network during the HighCapNMS
upgrade.
3.1.2.3 Required Disk Space for Upgrade and Restoring
Restoring previous database data requires double amount of free disk space
than the current DB size (\mysql\data\HighCapNMS). For example: if the
mysql\data\HighCapNMS directory size is 5 GB, there must be at least 10 GB
free space on the hard disk.
3.1.2.4 Time Required for Upgrade and Restoring
Backing-up and restoring the old database can take more than few hours.
If possible, it is recommended to perform the entire upgrade procedure in a
maintenance window.
To reduce the amount of needed disk space and time required for the upgrade
procedure, it is recommended to remove old records, especially those from
the PM tables. Removing these records can be performed manually or by
script.
Another option is to set HighCapNMS to Keep PM History for one day only.
This should be done one day before the upgrade.
To configure the PM history levels:
1 Select Start > Programs > HighCapNMS > HighCapNMS Server Config or
select Settings > Server configuration from the HighCapNMS Client menu
to open the HighCapNMS server config application.
2 Select the Polling tab.
HighCapNMS


3 In the Keep PM history field, configure the server to keep performance
monitoring data for 1 day.
4 Click Apply.
5 Click Close to exit the HighCapNMS server config utility.
3.1.2.5 User Directories
During upgrade only the following directories are kept untouched: config,
backup
All other directories are reloaded by the installer with the default files.
Before upgrade backup the following directories in case of using special
files.
/data: if there is important elements SW / config
/image: if there are external image files that are used.
3.2 Upgrading HighCapNMS on Windows Servers
3.2.1 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N7.0
This section contains instructions about how to upgrade servers on Windows
operating system from HighCapNMS N6.6.0.0.2/N6.6.0.1.2 to N7.0, without
keeping old data.
To upgrade to HighCapNMS N7.0 on a Windows operating system:
1 Export the current system topology:
i Open client application.
ii Select root.
iii Select File > Export Data and save the file to a safe location.
2 Backup the HighCapNMS license.
Copy license.crg from C:\Program Files\HighCapNMS\config
to a safe location.
HighCapNMS

3 Stop NMS processes.
Open the CLI window and run pvstop.
4 Backup the database. (for rollback only)
Change to the HighCapNMS directory and execute the pvdbbackup
command:
cd C:\Program Files\HighCapNMS
pvdbbackup backup C:\Program Files\HighCapNMS\backup\
backup_of_6_6.bcp
5 Verify that the database backup is successfully completed without any
error messages.
6 If you are using different FileZilla FTP account than the default, make a
backup of FileZilla Server.xml from C:\Program Files\FileZilla Server and
copy it into a safe location.
7 Run mysql_5.1_Install.exe to install MySQL 5.1.
Note: During the installation you may receive an error message
that states that you do not have Admin rights. Ignore the
message and select OK. Continue with the installation
process.
8 Hide the HighCapNMS icon.
Right-click the HighCapNMS icon in Windows notification area and
select Hide Tray Icon.
If the HighCapNMS icon does not exist, open the CLI window and
run pvstart.
Wait for all 7 processes to start and make sure you see
HighCapNMS icon in the Windows notification area.
Press Ctrl C to verify that all 6 processes are stopped and PV icon is
turned red
Press Enter and close the CLI window.
Right-click on the HighCapNMS icon and select Hide Tray Icon.
9 Run N7.0_Install.exe to install HighCapNMS.
10 Restart the computer.
11 Open the CLI window and run pvstatus to verify that 7 NMS processes are
running.
12 If you were using different FileZilla FTP account than the default, copy the
backup of FileZilla Server.xml back to C:\Program Files\FileZilla Server.
13 Restart the FileZilla Server FTP server from Windows Services.
14 Start HighCapNMS Client and verify that users can login without any
errors.
15 Select File > Import Data to import the saved topology information.
16 Wait several minutes while HighCapNMS collects new data from the NEs.
17 Select one element and perform a Poll Node operation on it to confirm
that all tasks have succeeded.
18 After completing the upgrade, inform HighCapRadio HQ about each server
that has been upgraded to MySQL 5.1 with the following details:
HighCapNMS

3.2.2 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N7.0 and Restoring Old
Data
Upgrading from HighCapNMS N6.6.0.0.2 / N6.6.0.1.2 to N7.0 is a two stage
process:
1 Upgrade to N6.6.1.5.1.
2 Upgrade to N.7.0.
3.2.2.1 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N6.6.1.5.1 with Data
Restoration
To upgrade from HighCapNMS N6.6.0.0.2 / N6.6.0.1.2 to N6.6.1.5.1 on a
Windows server:
ii Select root from the topology tree in the Navigator panel on the left.
iii Select File > Export Data and save the export file to a location outside
of the HighCapNMS directory.
Copy license.crg from C:\Program Files\HighCapNMS\config to a
safe location.
3 Stop NMS processes
Open the CLI and run pvstop.
4 Backup the database.
Change to the HighCapNMS directory and execute the pvdbbackup
command:
pvdbbackup backup C:\Program Files\HighCapNMS\backup\
backup_of_6_6.bcp
error messages.
backup of FileZilla Server.xml from C:\Program Files\FileZilla Server into
a safe location.
7 Run mysql_5.1_Install.exe to install MySQL 5.1.
message and select OK. Continue with the installation
process.
8 Right-click the HighCapNMS icon in Windows notification area and select
Hide Tray Icon.
i If the HighCapNMS icon does not exist open the CLI and run pvstart
HighCapNMS

ii Wait for all (7) processes to start and make sure you see the
HighCapNMS icon in the Windows notification area.
iii Press Ctrl+C to verify that 6 processes are stopped and that the PV
icon is red.
iv Press Enter and close the CLI window.
v Right click the HighCapNMS icon and select Hide Tray Icon.
9 Run N6.6.1.5.1_Install.exe to install N6.6.1.5.1.
11 Open the CLI and run pvstatus to make sure that all (7) HighCapNMS
processes are running
12 Run pvstop to stop the NMS processes.
13 If you are using a non-standard FTP server (not the FileZilla FTP server),
copy the backup of FileZilla Server.xml back to C:\Program Files\FileZilla
Server.
14 Restart the FileZilla FTP server from Windows Services.
15 Start HighCapNMS Client to verify that users can login without any errors.
16 Select File > Import Data to import the saved topology information.
3.2.2.2 Upgrading from N6.6.1.5.1 to N7.0 with Data Restoration
To upgrade from HighCapNMS N6.6.1.5.1 to N7.0 on a Windows server:
1 Close HighCapNMS Client.
2 Open the CLI window and run pvstop to stop NMS processes.
Hide Tray Icon.
i If the HighCapNMS icon does not exist, open the CLI window and run
pvstart.
ii Wait for all 7 processes to start and make sure you see HighCapNMS
icon on Windows notification area.
iii Press Ctrl+C to verify 6 processes are stopped and PV icon is turned
red
iv Press Enter and close CLI window.
6 Open the CLI and run pvstatus to verify that all 7 NMS processes are
running.
errors.
8 Select one element and perform a Poll Node operation on it. Confirm that
all tasks have succeeded.
HighCapNMS

3.2.3 Upgrading from N6.6.1.x.x to N7.0 and Restoring Old Data
Upgrading from HighCapNMS N6.6.1.x.x to N7.0 is a two stage process:
2 Upgrade to N.7.0.
3.2.3.1 Upgrading from N6.6.1.x.x to N6.6.1.5.1 with Data Restoration
To upgrade from HighCapNMS N6.6.1.x.x to N6.6.1.5.1 on a Windows server:
2 Backup the HighCapNMS license, copy license.crg from C:\Program
Files\HighCapNMS\config to a safe location.
3 Open the CLI and run pvstop to stop NMS processes.
Hide Tray Icon.
pvstart.
red
5 Execute N6.6.1.5.1_Install.exe to install N6.6.1.5.1.
7 Open the CLI and run pvstatus to make sure that all (7) HighCapNMS
processes are running
8 Run pvstop to stop the NMS processes.
backup of FileZilla Server.xml from C:\Program Files\FileZilla Server into
a safe location.
10 Restart the FileZilla FTP server from Windows Services.
11 Upgrade the database and convert old data into the new tables.
To convert PM data from old tables into the new database tables:
1 Open the CLI, change to the HighCapNMS directory.
2 Run UpgradeDB, specifying the number of days for PM history to be
converted into the database.
Usage: UpgradeDB -new=[days to restore]
For example, to convert only the last three days run:
UpgradeDB -new=3
If there is no need of restoring old data, run:
UpgradeDB -new=0
HighCapNMS

To convert all the history:
1 Run (or double click): UpgradeDB without any parameters.
error messages.
3 If you were using different FileZilla FTP account than the default, copy the
backup of FileZilla Server.xml to C:\Program Files\FileZilla Server.
4 Start the NMS server from Windows Services to start NMS processes.
errors.
3.2.3.2 Upgrading from N6.6.1.5.1 to N7.0. with Data Restoration
To upgrade from HighCapNMS N6.6.1.5.1 to N7.0 on a Windows server:
Hide Tray Icon.
pvstart.
red
6 Open the CLI and run pvstatus to verify that all 7 NMS processes are
running.
7 Run pvmap to open HighCapNMS Client and verify that users can login
without any errors.
8 Select one element and perform a Poll Node operation on it. Confirm that
all tasks have succeeded.
3.3 Upgrading HighCapNMS on Solaris Servers
3.3.1 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N7.0
This section contains instructions about how to upgrade servers on Solaris OS
from HighCapNMS N6.6.0.0.2 / N6.6.0.1.2 to N7.0, without keeping old data.
To upgrade from N6.6.0.0.2 / N6.6.0.1.2 to N7.0 on a Solaris server:
i Open the client application.
HighCapNMS

Copy license.crg from /opt/HighCapNMS/config to a location outside of
the HighCapNMS directory.
3 Run pvstop and pkill to stop NMS processes.
pvstop
pkill -9 java
4 Change to the HighCapNMS directory and run pvdbbackup to back up the
database.
pvdbbackup backup /opt/HighCapNMS/backup/
backup_of_xxx.bcp
error messages.
6 Open the terminal and stop the MySQL 4.1.7 process.
7 Change to the opt/mysql directory and run rm to verify that there is only
a single line of output.
cd /opt/mysql
rm r *
8 Install MySQL 5.1.
i Move the MySQL install file to the install directory. Make sure to
transfer the file as binary if you are moving it via FTP.
ii Open the terminal, change to the opt/install directory and enable the
necessary permissions to execute the MySQL installer.
cd /opt/install
chmod 775 mysql_5_1_Install.bin
./mysql_5_1_Install.bin
message and select OK. Continue with installation process.
9 Run a grep command to verify that MySQL is working.
If the output is less than two lines, repeat the installation.
10 Install N7.0.
i Move the N6.7.0 install file to the install directory. Make sure to
necessary permissions to execute the HighCapNMS installer.
cd /opt/install
chmod 775 N6_9_Install.bin
./N6_9_Install.bin
HighCapNMS

11 Run pvstart & to start the NMS processes.
12 Run pvstatus to confirm that HighCapNMS processes are running.
13 Open HighCapNMS Client or run pvmap & to verify that users can login
without any errors.
14 Select File > Import Data to import the saved topology data.
3.3.2 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N7.0 and Restoring Old
Data
Upgrading from HighCapNMS N6.6.0.0.2 / N6.6.0.1.2 to N7.0 is a two stage
process:
2 Upgrade to N.7.0.
3.3.2.1 Upgrading from N6.6.0.0.2 / N6.6.0.1.2 to N6.6.1.5.1 with Data
Restoration
To upgrade from HighCapNMS N6.6.0.0.2 / N6.6.0.1.2 to N6.6.1.5.1 on a
Solaris server:
Copy license.crg from /opt/HighCapNMS/config to a location outside of
the HighCapNMS directory.
3 Run pvstop and pkill to stop NMS processes.
pvstop
pkill -9 java
4 Open the terminal, change to the opt/HighCapNMS directory, and run
pvdbbackup to backup the database.
cd /opt/HighCapNMS
pvdbbackup backup /opt/HighCapNMS/backup/backup_of_6_6.bcp
error messages.
HighCapNMS

6 Copy the files dumpBeforeUpgrade and restoreAfterUpgrade files from
the installation directory to /opt/HighCapNMS.
Make sure to transfer the file as ASCI if you are moving them via FTP.
7 Change to the /opt/HighCapNMS directory and execute
dumpBeforeUpgrade to backup the data of the existing database into a
dump file (backup.sql).
cd /opt/HighCapNMS
chmod 777 dumpBeforeUpgrade
./dumpBeforeUpgrade
Note: This backup operation requires free disk space that is at
least double the size of the current database size (check the
size of /mysql/data/HighCapNMS).
8 Verify that the process completes successfully and without any error
messages. There should be a file named backup.sql in the
/opt/HighCapNMS/backup directory.
10 Change to the /opt/mysql directory and run rm to verify that there is only
cd /opt/mysql
rm r *
11 Install MySQL 5.1.
cd /opt/install
chmod 775 mysql_5_1_Install.bin
./mysql_5_1_Install.bin
13 Change to the opt/HighCapNMS directory and execute
restoreAfterUpgrade to restore the database.
cd /opt/HighCapNMS
chmod 775 restoreAfterUpgrade
./restoreAfterUpgrade
HighCapNMS

14 Install N6.6.1.5.1 to the opt/HighCapNMS directory.
i Move the N6.6.1.5.1 install file to the install directory.
Make sure to transfer the file as binary if you are moving it via FTP.
cd /opt/install
chmod 775 N6_6_1_5_1_Install.bin
./N6_6_1_5_1_Install.bin
15 Upgrade the database and convert old data into the new tables.
Change to the HighCapNMS directory and run UpgradeDB, specifying
the number of days for PM history to be converted into the database.
Usage: UpgradeDB -new=[days to restore]
For example, to convert only the last three days run:
cd opt\HighCapNMS
chmod 775 UpgradeDB
UpgradeDB -new=3
If there is no need of restoring old data, run:
UpgradeDB -new=0
To convert all the history:
Run UpgradeDB without any parameters.
Note: This operation might take a long time.
16 Confirm that all tasks have succeeded without error messages.
without any errors.
20 Select File > Import Data to import the saved topology data.
To upgrade from HighCapNMS N6.6.1.5.1 to N7.0 on a Solaris server:
2 Open the terminal and run pvstop to stop NMS processes.
Right-click on the HighCapNMS icon in Windows notification area and
4 Install N7.0 to /opt/HighCapNMS.
i Move the N6.7.0 install file to the install directory.
Make sure to transfer the file as binary if you are moving it via FTP.
HighCapNMS

cd /opt/install
./N6_9_Install.bin
without any errors.
3.3.3 Upgrading from N6.6.1.x.x to N7.0 and Restoring Old Data
Upgrading from HighCapNMS N6.6.1.x.x to N7.0 is a two stage process:
2 Upgrade to N.7.0.
3.3.3.1 Upgrading from N6.6.1.x.x to N6.6.1.5.1 with Data Restoration
To upgrade from HighCapNMS N6.6.1.x.x to N7.0 on a Solaris server:
Copy license.crg from /opt/HighCapNMS/config to a safe location.
3 Run pvstop to stop NMS processes.
4 Install N6.6.1.5.1.
i Move the N6.6.1.5.1 install file to the install directory. Make sure to
ii Open the terminal and change to the install directory.
iii Enable write permissions on the installation file, and install the
upgrade to the current HighCapNMS location (usually
/opt/HighCapNMS).
cd /opt/install
chmod 775 N6_6_1_5_1_Install.bin
./N6_6_1_5_1_Install.bin
5 Confirm that all tasks have succeeded without error messages.
without any errors.
9 Select File > Import Data to import the topology file that you exported in
Step 1.
HighCapNMS

To upgrade from HighCapNMS N6.6.1.5.1 to N7.0 on a Solaris server:
Right-click on the HighCapNMS icon in Windows notification area and
4 Install N7.0 to /opt/HighCapNMS.
i Move the N6.7.0 install file to the install directory. Make sure to
cd /opt/install
./N6_9_Install.bin
without any errors.
3.4 Upgrading servers in Redundancy Mode
This section contains instructions about how to upgrade servers in
redundancy mode without losing network management.
Each step describes which server is being configured.
The steps descriptions are general and the same for both Windows and Solaris
OS.
Follow the steps according to the instructions above per HighCapNMS current
version for a stand-alone server (previous chapters).
There is great significance for the order of the steps, since servers
synchronization during incompatible versions can damage.
3.4.1 Prerequisites
To upgrade a redundant system, verify that
Server redundancy functionality is configured correctly in both the main
and standby servers.
HighCapNMS clients only are configured to use the Standby server if the
Main is down.
All network elements are configured to send traps to both the main and
standby servers.
HighCapNMS

3.4.2 Upgrading the Main and Standby Servers
To upgrade main and standby servers:
1 Stop HighCapNMS processes in both the Main and the Standby servers.
2 Set both servers to standalone mode.
Run pvconfig to open the HighCapNMS Server Config utility.
In the Redundancy tab, set the Server Role to Stand Alone Server.
3 Start NMS process on the Standby server.
4 Set remote clients to connect to the standby server.
Clients should be connect to the standby server and continue working
in standalone mode.
WARNING: Do not add new NEs or change the topology. These changes
are not configured in the Main server after the upgrade
process is completed.
5 Begin with the upgrade procedure on the Main server according to
instructions for a stand-alone server.
6 From the Standby server, stop NMS processes.
7 Start NMS processes on the Main server.
8 Upgrade remote clients and reconfigure remote hosts settings for Main
and Standby as they were before upgrade.
If you are upgrading from version N6.7 or higher, an automatic client
upgrade will be performed.
Clients should be connect to the Main server and continue working in
standalone mode.
9 Begin with the upgrade procedure on the Standby server according to
instructions for a stand-alone server.
Warning: Do not start NMS processes on Standby yet.
10 Open HighCapNMS Server Configuration for the Main server.
11 Click the Redundancy tab and set the Server Role to Main Server.
12 Restart NMS processes in the Main server.
13 Open HighCapNMS Server Configuration for the Standby server.
14 Click the Redundancy tab and set the Server Role to Standby Auto Switch.
15 From the Standby server, restart NMS processes.
16 Wait for Standby to receive all topology from the Main server to verify
communication between the servers.
Note: Synchronization between the Main and Standby servers
may take a long time if the database is big.
17 Inform HighCapRadio HQ after every server that has been upgraded to
MySQL 5.1 with the following details:
HighCapNMS

3.5 Downgrading to HighCapNMS N6.6.0.1.2
3.5.1 Downgrading to HighCapNMS N6.6.0.1.2 on Windows Servers
To downgrade HighCapNMS to N6.6.0.1.2 on a Windows server:
ii Select root.
Copy the license.crg file from C:\Program Files\HighCapNMS\config to
a safe location.
4 Execute MySql_417D.exe to install MySQL 4.1.7.
5 Open Windows Task Manager to verify that MySQL is running.
6 Select Settings > Control Panel > Add/Remove Programs to uninstall
HighCapNMS.
After uninstalling HighCapNMS, the subfolders backup and config
should be remain under C:\Program Files\HighCapNMS.
7 Right-click the HighCapNMS icon in the Windows notification area and
select Hide Tray Icon from the context menu.
If the HighCapNMS icon does not exist:
i Open the CLI window and run pvstart.
iii Press Ctrl + C to verify that 6 processes are stopped and that the PV
icon is turned red.
iv Press Enter and close the CLI window.
v Right-click the HighCapNMS icon and select Hide Tray Icon from the
context menu.
8 Execute the N6.6.0.1.2.1041.exe installer to install HighCapNMS
N6.6.01.2.
After the computer is restarted the HighCapNMS processes should be
running.
11 Change to the C:\Program Files\HighCapNMS folder and run createdb to
create a new (empty) database.
createdb create
12 Verify that the new database is successfully completed without any error
messages.
HighCapNMS

13 Open the CLI window, change to the C:\Program Files\HighCapNMS
directory, and run pvdbbackup to restore data from the bcp file.
pvdbbackup restore C:\Program Files
\HighCapNMS\backup\backup_of_6_6.bcp
14 Start the NMS server from Windows services to start NMS processes.
15 Run pvmap to open HighCapNMS Client and verify that users can login
without any errors.
16 If you did not restore your old database data, select File > Import Data to
import the saved topology data.
3.5.2 Downgrading to HighCapNMS N6.6.0.1.2 on Solaris servers
To downgrade to HighCapNMS N6.6.0.1.2 on a Solaris server:
ii Select root.
2 Backup the HighCapNMS license,
Copy the license.crg file from /opt/HighCapNMS/config to a safe
location.
3 Open a terminal and run pvstop to stop NMS processes.
5 Change to the /opt/mysql directory and run rm to verify that there is only
cd /opt/mysql
rm r *
6 Install MySQL 4.1.7.
cd /opt/install
chmod 775 mysql_4_1_7_Install.bin
./mysql_4_1_7_Install.bin
HighCapNMS

8 Change to the opt/HighCapNMS/UninstallerData directory and enable the
necessary permissions to execute the HighCapNMS uninstaller.
cd /opt/HighCapNMS/UninstallerData
chmod 775 Uninstall_NMS_Type
./UninstallHighCapNMS
9 Install N6.6.0.1.2 to the opt/HighCapNMS directory.
i Move the N6.6.0.1.2 install file to the install directory. Make sure to
cd /opt/install
chmod 775 N6_6_0_1_2.bin
./N6_6_0_1_2.bin
11 Change to the opt/HighCapNMS directory and run createdb to create a
new (empty) database.
12 Confirm that the database is created successfully and without error
messages.
13 Change to the HighCapNMS directory and run pvdbbackup to restore
version 6.6 data from the bcp backup file:
cd /Program Files/highcapnms
pvdbbackup restore /opt/highcapnms
backup/backup_of_6_6.bcp
14 Open the terminal and run pvstart & to start NMS processes.
15 Run the pvstatus & command to verify that HighCapNMS processes are
running.
16 Run pvmap & to start HighCapNMS Client and verify that users can login
without any errors.
17 If you did not restore your previous database, select File > Import Data to
import the saved topology information.
HighCapNMS

4. Testing Server Installation
4.1 Testing a Standalone Server Installation
After installation, open the Terminal.
Run "pvstart &" and make sure that the following messages appear:

Run VarioManager, see that the following login screen appears, and click
Cancel.

Make sure that HighCapNMS icons appear in the menu bar as follows:
Run "pvmap &".
When the Login screen appears, enter the following - User Name: admin,
Password: admin.
HighCapNMS


Important Note! For security reasons, it is highly recommended to change
the preset admin users user name and password from the
default values admin and admin.

Additionally, if there is any risk of unauthorized access from
within the organization, it is recommended not to select
Save Password in the login screen.
Make sure the map is loaded properly, the server appears on the map, and it is
colored green.

Run "cmconfig" and select the Advanced tab.
Make sure that "/usr/sfw/bin/mozilla" appears in the web browser.
HighCapNMS


4.2 Testing Redundant Servers
To test a redundant server implementation:
1 Perform the HighCapNMS server installation procedure for each of the
servers.
2 Perform the HighCapNMS Standalone Server Testing procedure for each
the servers.
3 On the main server, run pvconfig.
4 Click the Redundancy tab, and for the main server, select the Server role.
5 Click Apply, and then Close.
6 In the terminal, run pvstop, and then pvstart.
7 On the Standby server, run pvconfig.
8 Click the Redundancy tab, and for the Standby-Auto Switch, select the
Server role.
9 For Main Server Host Address, enter the main servers IP address.
10 For Main-Standby Synchronization, select Full.
11 Click Apply, and then Close.
12 In the terminal, run pvstop, and then pvstart.
13 On the Main server, run pvmap. Make sure the map is loaded properly, the
server appears on the map, and it is colored green.
14 Right click anywhere on the map and select Add group.
15 Choose a name for the group and click OK.
16 Make sure that the group is added to the map.
17 On the Standby server, run pvmap. Make sure the map is loaded properly,
the server appears on the map, and it is colored green.
18 Make sure that the group you added on the main server appears in the
map.
HighCapNMS

5. Configuring your System
5.1 Configuring the FTP Server
Note that login information in the FTP server must match the FTP login
information that you enter in the File Transfer tab of HighCapNMSs server
configuration utility.
For Windows servers, the FileZilla FTP server must be installed before
installing HighCapNMS. The FileZilla FTP server should be installed under:
C:\ProgramFiles\FileZilla Server\.
Solaris and HP servers use the operating system's built-in FTP server, and
dont require the FileZilla server.
To configure the FTP server for Unix:
1 Connect as a root user.
2 Run passwd ftpuser and configure your login settings.
To configure the FTP server for a HighCapNMS server running on MS
Windows:
After installing HighCapNMS, open the FTP server.
1 Create a user (called "ftpuser"), and set the password.
2 Set the home directory to install\highcapnms\data and enable all
permissions.
3 In the HighCapNMS server configuration window, click the File transfer
tab and configure the settings.
5.2 HighCapNMS Server Configuration
To configure the HighCapNMS server:
1 Run the pvconfig command, select Start > Programs > HighCapNMS >
HighCapNMS server config, or select Settings > Server configuration
from the HighCapNMS Client menu.
2 Click Restore defaults to reset configuration parameters to their original
values.
3 Click Reload page to reload the page with the last saved values.
4 Click Apply to save changes.
5 Click Close to exit the HighCapNMS server config utility.
HighCapNMS

5.2.1 General Settings
In the General tab, configure server general parameters.

NMS server TCP port number Define which TCP port the server should
use to listen to HighCapNMS Client clients.
SMTP (email) server address Specify the IP address or hostname of the
SMTP mail server.
Sent by email address Specify the Sent by email address to be used
when the server sends reports by email.
User actions logger port number Specify the port number for logging
user actions.
Keep actions history Specify the number of days to keep user action
history records.
Enable ENM proxy Enable the NMS to act as a proxy server when the
ENM doesn't have direct access to a network element.
Note that to enable this option, the ENM must be capable of working
via a proxy.
ENM proxy port number Specify the ENM proxy port from which
HighCapNMS will receive proxy requests.
HighCapNMS

Enable HTTP(S) proxy Enable the NMS to act as a HTTPS proxy server
when the web browser doesn't have direct access to a network element.
Note that you must also configure your web browser to recognize
HighCapNMS as a proxy server.
HTTP proxy port number Specify the HTTP proxy port from which
HighCapNMS will receive proxy requests.
Max number of Ethernet services to display Specify the maximum
number Ethernet services to display in Service views EVC list. The
minimal allowed value is 100. The maximal allowed value is 10000.
Enable Ethernet service When Ethernet Services are licensed, selecting
True enables the NMS server to collect Ethernet services information from
the network elements.
5.2.2 Polling Settings
In the Polling tab, configure polling related parameters.

Dynamic polling interval Specify how often the server should poll
network elements for dynamic inventory data.
The value will be rounded out to the nearest quarter of an hour.
Reports polling interval Specify how often the server should poll
network elements for performance monitoring data.
Config upload interval Specify how often the server should upload
(backup) configuration files from network elements.
Alarms polling interval Specify how often the server should poll
network elements for current alarm data.
Keep PM history Specify the number of days to keep performance
monitoring report data in the database.
HighCapNMS

5.2.3 File Transfer Settings
In the File transfer tab, configure file transfer related server parameters.

TFTP server address Specify the IP address or hostname of the TFTP
server.
TFTP files location Specify a relative or absolute path to network
element software files.
The folder name cannot contain spaces.
TFTP timeout Specify how many seconds to wait for the TFTP server
response before considering a TFTP request as timed-out.
TFTP retries Specify the maximum number of allowed retries after a
TFTP timeout.
FTP server protocol Specify FTP or SFTP as the file transfer server
protocol.
FTP server address Specify the IP address or hostname of the FTP
server.
FTP server username Specify the username for the FTP server.
FTP server password Specify the password for the FTP server.
HighCapNMS

5.2.4 Security Settings
In the Security tab, configure security related parameters.

Inactive client disconnect time Specify the number of minutes the
server should wait before disconnecting an inactive client.
Setting this value to 0 will allow inactive clients to remain connected
indefinitely.
The maximum value is 30,000 minutes.
Allowed consecutive failed logins Specify the number of times a user
can attempt to login before being blocked.
After the specified number of login attempts, a management trap will
be issued, and the user will not be able to log in again for the amount of
time specified by the Block user period.
Setting this value to 0 will allow an infinite number of login attempts.
Block user period Specify the number of minutes a user will not be able
to log in after reaching the maximum number of allowed retries.
Setting this value to 0 will disable this feature.
Secured client connection Enforce a secure connection between the
client and server.
When set to True, the server will reject non-secure connections.
Important Note! It is recommended to set Secured client connection to
True in order to protect the network from replay security
attacks.
Radius mode Enable or disable RADIUS authentication. When RADIUS
authentication is enabled:
HighCapNMS

If the Radius server is available, users will be authenticated by the
RADIUS server.
If the RADIUS server is not available, the user will be authenticated
locally.
If the RADIUS server rejects the user, no further authentication will be
performed locally, and the user will not be able to log in.
For the user with the user name admin, HighCapNMS enables you to
configure whether this user is authenticated locally or by RADIUS. If
you choose to authenticate the admin user locally, the admin user will
always be authenticated locally and not by RADIUS, even when the
RADIUS server is available.
Radius server host Specify the IP address or hostname of the Radius
authentication server.
Radius authentication of the administrator - When this parameter is
set to Enable, the admin user (User Name = admin) is authenticated via
RADIUS like other users. When this parameter is set to Disable, the admin
user (User Name = admin) is authenticated locally, even if RADIUS is
enabled. The purpose of this option is to ensure that a system
administrator can always access the system even if there is a problem with
the RADIUS configuration.
Radius authentication port number Enter the number of the port to
use for RADIUS authentication. The default value is 1812.
Radius Server Login timeout Specify how many seconds to wait for a
response from the RADIUS server. Options are 3-30. The default value is 5.
Radius Server Number of Login retries Specify the number of retry
attempts in case the RADIUS server is initially unavailable. Options are 1 -
10. The default value is 3.
Radius Server Secret Specify the shared secret for external
authentication. This can be an alphanumeric string up to 128 characters.
HighCapNMS

5.2.5 Redundancy Settings
In the Redundancy tab, configure main and standby server operation.

Server role Specify the role of this server when a redundant
configuration is used.
In a redundant configuration there are two servers. The standby server
is used when the main server is not available.
Stand alone server - The default setting. No redundancy is
configured.
Main server - The server is configured as a main server, which will
be connected to a secondary server. If no secondary server exists,
an alarm will be raised.
Standby - Auto switch - The server is configured as a secondary
server. After disconnection from the main server for a user
specified number of minutes, it will automatically take over from
the main server.
Main server host address Specify the IP address or host name of the
main server.
This parameter is only relevant if you selected Standby as the server
role.
Connection timeout to standby server Specify the number of minutes
after which the main server will generate an alarm if it was disconnected
from the standby server.
The minimum time is one minute. The maximum time is 120 minutes.
This parameter is only relevant if you selected Main as the server role.
HighCapNMS

Standby activate time Specify the number of minutes after which the
standby server will be active when the connection to the main server is
down.
role.
Standby deactivate time Specify the number of minutes after which the
standby server will be muted when the main server resumes operation.
role.
Main-standby synchronization Choose a synchronization mode
between the main and the standby servers.
Disabled disables the synchronization feature.
Full causes changes in one server (main or standby) to be made in the
other server as well.
Only from main to standby - (recommended setting) causes changes
in the main server to be made in the standby server as well, but not
vice versa.
Only from standby to main - causes changes in the standby server to
be made in the main server as well, but not vice versa.
Sync interval Specify the number of minutes between synchronization
updates between the main and standby servers.
Auto activate the standby server Admin state upon which the Main
server will active the Standby server if the threshold of unreachable NE
was crossed.
Note, in this case the Main server and the Standby server will be active.
Main server management threshold Specify the percentage of
unreachable network elements that will force a switch to the standby
server.
Upon crossing this threshold, the standby server will switch to Active
state only if the standby server management threshold has not been
crossed.
Standby server management threshold Specify the percentage of
unreachable network elements that will mute the standby server.
Upon crossing this threshold, the Standby server will switch to Mute
state only if the main server management threshold has not been
crossed.
Mute standby server poll mode Choose a polling option for the
secondary server.
role.
No data polled - When the secondary server is in standby mode, polling of
data from network elements will be disabled.
Poll only alarms - This is the recommended and default setting. When the
secondary server is in standby mode, only alarm information will be polled
from network elements.
HighCapNMS

Poll alarms and inventory - When the secondary server is in standby
mode, only alarm and inventory information will be polled from network
elements.
Poll all data - When the secondary server is in standby mode, all data will
be polled from network elements. In this configuration all data will be
polled by both the primary and the secondary servers.
5.2.6 Alarms Settings
In the Alarms tab, configure alarm related parameters.

Email format Select the format you want for email messages triggered
by alarms. Available formats are HTML and Plain Text. If you select,
HTML, you can use HTML tags to control the way the messages appear.
Max number of initial alarms Specify the maximum number of alarms
to show in the alarm logs window.
The minimum number of initial alarms is 1000.
The maximum number of initial alarms is 50,000.
Note that while the window is open, new alarms will be added to the
alarms log as they are received.
Ignore heartbeat Heartbeats are traps that are sent out by network
elements at user defined intervals. Setting this parameter value to True
will make the server ignore the heartbeat traps received from the network
elements.
Keep alarms history Specify the number of days to keep alarm log
history data in the database.
Alarm data will always be kept for at least five days, and can be kept for
an entire year.
Note that alarms that are open (raised) will be kept until they are
closed, regardless of the value you set for this option.
HighCapNMS

5.2.7 Advanced Settings
In the Advanced tab, configure additional server parameters such as CPU load,
disk space threshold interface language and application time zone.

Max concurrent tasks Specify the maximum number of network
element polling tasks that the server can run simultaneously.
VC calculation from KLM Use KLM values to define the formula for
calculating the virtual container.
Select interface language Select the language in which you want user
interface to appear.
Additional languages require a separate software license.
Max memory allocation Specify the maximum amount of memory the
application can allocate. The minimum is 256 MB, the maximum is 8192
MB.
For large scale networks, increase the Max Memory Allocation size to
~1/3 the total memory in the computer. For example, if the computer
is fitted with 2GB memory, set this value to around 700MB.
Application time zone Specify the time zone to be used. You only need
to specify the zone if the application time is not calculated correctly. If the
time zone is already configured correctly, you can leave this field empty.
The format is GMT+/-<offset> with no spaces between the parameters,
for example: GMT+2.
Threshold of free disk space Specify the amount of free disk space
below which an alarm will be generated.
Threshold of average CPU load Specify the system load average above
which an alarm will be generated.
HighCapNMS

5.3 HighCapNMS Client Configuration
To configure the HighCapNMS Client client:
1 Select Start > Programs > HighCapNMS > HighCapNMS Client Client
Config, or select Settings > Client configuration from the HighCapNMS
Client menu.
2 Click Restore defaults to reset configuration parameters to their original
values.
3 Click Reload page to reload the page with the last saved values.
4 Click Apply to save changes.
5 Click Close to exit the HighCapNMS Client Client config utility.

Displayed entity name format Select the format for the element name
that represents the element in the map. The available formats are name
only, IP address only, or both name and IP address.
Display link name on map Specify whether or not to display link names
on the map. When hidden, you can view the link names via their tooltips.
Default link width Specify the default width of the line that will
represent a link between two elements in the map.
Map background color Select the color for the map background through
a color choose pallet, specifying HSB or RGB values.
Max number of trigger messages Specify the maximum number of
trigger messages to be displayed for the user. When the number of triggers
exceeds this number, older messages will be deleted.
To optimize performance, lines are deleted in batches instead of one by
one. In-between batch deletions, the actual number of displayed
messages may exceed the specified threshold.
HighCapNMS

Max PM report lines Specify the maximum number of entries to retrieve
when a performance monitoring report is requested.
5.3.2 Remote Hosts Settings

Primary NMS server host address Specify the IP address or hostname
of the primary server.
Primary NMS server TCP port number Specify the TCP listening port
of the primary server. The value of this parameter should match the value
configured for the NMS Server TCP Port Number parameter on the
primary server.
Secondary NMS server host address Specify the IP address or
hostname of the secondary server.
Secondary NMS server TCP port number Specify the TCP listening port
of the secondary server. The value of this parameter should match the
value configured for the NMS Server TCP Port Number parameter on the
secondary server.
HighCapNMS


Play sound minimal gap Specify the number of seconds between
sounds for a triggered alarm.
Windows refresh interval Specify the number of seconds between
information updates in HighCapNMS Client windows.
Media files upload interval Specify the number of minutes for
HighCapNMS to wait between media file updates.
Media files include map background images and audio files and are
stored in the HighCapNMS directory.
Connection check interval Specify the interval in seconds for the client
to check its connection with the HighCapNMS server.
Select interface language Select the user interface language for the
HighCapNMS Client.
Note that additional languages require a separate software license.
Application time zone Specify the time zone to be used. You only need
to specify the zone if the application time is not calculated correctly. If the
time zone is already configured correctly, you can leave this field empty.
The format is GMT+/-<offset> with no spaces between the parameters,
for example: GMT+2.
FTP server username Specify the ftp username, which will be used for
communication with the HighCapNMS server during automatic upgrade of
the HighCapNMS Client client software.
5.4 Client Browser Configuration
For each browser that will be used to manage network elements:
1 Open a browser window.
2 Select Internet options from the Tools menu.
HighCapNMS

3 Select the Connections tab.
4 Click LAN Settings.
5 In the Proxy Server area, select Use a proxy server for your LAN.
6 In the address area, specify the address of the machine on which the web
proxy server is installed.
7 For Port, enter 8080 (or a different port number if configured otherwise in
the web proxy server).
5.5 Trap Forwarding
PV can forward NMS specific management traps and SNMP traps that arrive
from the network elements to one or more northbound OSS.
To receive traps from network elements, HighCapNMS must be configured as
one of the network elements trap managers.
This can be done using configuration Broadcast feature on a single or a group
of elements.
To configure network element manually to send traps to HighCapNMS:
1 Open the network elements web EMS.
2 Select Configuration > General > Traps Configuration.
3 Expand a trap manager to configure its settings.

In the Trap Managers section:
1 Select Enable from the Traps admin field drop down list.
2 Specify the IP address to which traps will be sent.
In the Trap manager field, enter the destination IP address.
HighCapNMS

3 Specify HighCapNMS as the trap manager in the Manager name field.
4 Configure 162 as the sending port in the Trap port field.
5 In the SNMP trap Community field, enter the SNMP community name.
6 In the Heartbeat period field, specify the number of minutes between
generating heartbeat traps.
7 In the Trap CLLI field, enter free text to be sent with the trap.
8 Specify trap forwarding criteria.
In the Trap status change filter field, select On if you want a trap to be
sent to the manager you defined only when the most-severe alarm of
the unit changes.
In the Send traps for alarms with severity field, select which severity
levels of alarms will be forwarded.
9 Click Apply.
To configure network elements for trap forwarding:
Deselect Report traps of far end IDU
Select Use different alarm ID for each alarm type
Select Send traps with extended alarm information
To configure trap forwarding:
1 Select Start > Programs > HighCapNMS > Trap forwarding config, or
select Settings > Trap forwarding options from the HighCapNMS Client
menu to open HighCapNMSs frap forwarding utility.
2 Specify the trap forwarding parameters, and click Apply to save changes.
Click Restore defaults to reset configuration parameters to their
original values.
Click Reload
In addition, remember to configure the network elements to send traps to the
listening port that you specify here.
HighCapNMS

Set general trap forwarding parameters, such as the forwarding mode and the
trap listening port number.

Trap forwarding mode Specify the trap forwarding mode.
Off Disables trap forwarding.
Regular Forwards the trap exactly as it was received.
NSN Translates the trap for NSNs NetAct application.
NSN alarm synchronization Supports incoming alarm translation and
NSN's NE3S agent.
Note: If the mode is set to Regular, NSN or NSN alarm
synchronization, all network elements must send the traps to the
port specified in the Trap listening port field.
If the mode is set to Off, all network elements must send traps
directly to the Management alarms port that you specified in the
Advanced configuration tab.
Trap listening port Specify the trap listening port. The standard port is
162. Change this number if it is already being used by another SNMP
service.
Local host address Specify the IP address or hostname of the local host.
Leave the value 0.0.0.0 to bind all IP addresses.
Forward traps to host Specify the list of host names and port numbers
to which traps will be forwarded. Use the format <host IP>:<port>.
HighCapNMS

5.5.2 OSS Settings
Set trap forwarding parameters specific to the OSS network management
application.

SNMP agent address Specify the IP address.
SNMP agent port number Specify the agent port.
NMS server ID Define a unique ID for the OSS NMS server.
In the NMS server ID field, you may want to change the value When
multiple NMS servers are connected to the same NSN server, make
sure that each NMS server has a unique ID.
Configure advanced trap forwarding parameters, such as management alarms
port and the heartbeat interval.

Heartbeat interval Specify the number of minutes between generating
Heartbeat traps from network elements to inform the server that the
system is working.
HighCapNMS

Setting this value to 0 will disable heartbeat trap forwarding.
Management alarms port Specify the internal port used to send
management alarms to the trap forwarding hosts.
Auto add network element Enable or disable automatically adding a
new network element to the map as soon as a trap from an unknown IP
address was received.
Send cleared traps with zero severity Enable or disable sending
cleared traps with zero severity.
Select Enable to forward cleared traps with zero severity.
Select Disable to forward the cleared trap with the severity of the
raised alarm.
This setting will not affect cleared traps that are forwarded directly
from network elements to the trap forwarding hosts.
5.6 DCN Sizing
DCN sizing helps determine the required bandwidth between the network
elements and the centralized network management system.

5.6.1 HighCapNMS Server - HighCapNMS Client Client
The NMS should have IP connectivity to the network element network.
HighCapNMS clients can be locally installed on the Sever or remotely installed
on a separate PC.
The client PCs can be directly connected to the network element network. If
no DCN connection is available between the HighCapNMS clients and the
network element network, the HighCapNMS server can be used as a proxy
server. SNMP or HTTP requests from the client will be sent to the network
through the HighCapNMS server.
HighCapNMS

The minimum recommended bandwidth between the HighCapNMS server and
any remote connected HighCapNMS client user (HighCapNMS Client) is 2
Mbps.
Recommended bandwidth between HighCapNMS server and active
connected HighCapNMS clients:
Number of Clients 1 2 5 10 20
Recommended DCN
Bandwidth towards the
HighCapNMS Server
2048 Kbps 2048 Kbps 4096 Kbps 10 Mbps 20 Mbps
5.6.2 HighCapNMS Server - Network Element Network
The recommended bandwidth between the HighCapNMS server and the first
network element on the NE network is driven by the number of NEs that need
to be managed on this single DCN connection and the application in use.
For one NE Telnet/SSH CLI connection, a 128 Kbps connection suffices.
For a typical Web or HighCapNMS connection 1 Mbps is recommended
(where 512 Kbps is the minimum).
2 Mbps is recommended for larger networks.
5.6.3 Local Connection to the Network Element
Users can directly connect to the NE using a local connection, via the CLI or the
Web EMS. The recommended bandwidth for directly connected users with a
CLI connection is 128 Kbps. The Web EMS requires a minimum of 512 bps
bandwidth connection.
5.6.4 HighCapNMS Northbound Interface
Northbound interfaces should be treated as client connections. This means
that the sizing rules of the HighCapNMS Server - Client should be used here as
well.
5.6.5 Redundant Server Solution - HighCapNMS
HighCapNMS includes built-in support for redundancy configuration. This
configuration includes two HighCapNMS servers: a primary server, which is
generally active, and a secondary server, which is generally located at a
geographically remote site, and is in standby mode. To keep the information
on both servers synchronized, an Ethernet connection should be available
between the two servers.
The recommended bandwidth between the Main Server and the Standby
server is 2 Mbps.
HighCapNMS

Note: The HighCapNMS standby server may have lower
bandwidth connection depending on the configuration in
case the main server it up. The standby server may be
configured not to poll any info from the NE, while
synchronizing only from the main server; however, if the
Main server is down, the standby server need to have the
same bandwidth as the main server.

5.7 Ethernet Services Pre-Configuration
5.7.1 Pre-Configuration Overview
The Ethernet Services feature was introduced in HighCapNMS version N6.7.
This feature includes configuration and retrieval of Ethernet Services data
from the XPAND IP+ network elements.
The following are the main features of the HighCapNMS Ethernet services
component:
Retrieving the Ethernet services in the network according to network
element data.
Ethernet service provisioning
Proposing a path for the service requested by user
Constructing new services according to user requests.
5.7.1.1 Concepts and Acronyms
To create and maintain services using the services GUI, it is necessary to know
the topology of the network (how the different network elements are
interconnected).
HighCapNMS

Network elements contain information about their peers IP addresses as a
series of parameters in the IP table. The IP table contains information about
the physical connections of each relevant traffic port to other ports or network
elements. The table contents may be manually configured or automatically
detected by the use of the LLDP protocol.
A Peer is an XPAND IP+ network element connected through either radio or
Ethernet or STM1/OC-3 port to the network element.
5.7.1.2 Acronyms
SAP Service Access Point
SNP Service Network Point
LAG Link Aggregation
Supported network elements for Ethernet services include:
XPAND IP+ R2/R3 with minimum version I6.7 software, in either nodal or
standalone mode.
Unless indicated otherwise, configuration details are for both modes.
Support for XPAND IP+ R1 6.3.2 is limited and will not be addressed in this
document.
5.7.2 IP Table Configuration
IP table information must be either manually entered by users or be
automatically determined by enabling LLDP (transmit and receive mode) for
both sides in the relevant ports in the elements.
Notice that the IP table may include also information regarding OC-3/STM-1
ports. This data is used by the TDM trails feature, but is not necessary for the
Ethernet services.
Examples of IP-table configuration are shown below. Note that in the example,
Ethernet port #8 is the Ethernet port embedded in the radio port.
Figure 1: IP Table, Example #1

HighCapNMS

Figure 2: IP Table, Example #2

5.7.2.1 Ethernet Peer Ports Configuration
Unless LLDP is enabled in both sides in the elements Ethernet peer ports must
be configured manually.
User must configure the information for every traffic port which is connected
directly to another port (that is, the peer port in the network, except for the
service end-point ports).
The configuration must be done in all cases, whether the peer is another port
of same network element (standalone), or in another slot of same network
element (nodal or in a different network element, and whether the Ethernet
application is switch or single pipe.
5.7.2.2 Exceptions
Ethernet port #8
There is no need to configure manually Ethernet port #8. Ethernet port #8
is the Ethernet port connected to the Radio link.
As Radio remote peer is automatically discovered by network element, and
read by HighCapNMS directly from the Remote Radio Parameters, Remote
IP address, both HighCapNMS and the network element ignore anything
configured in the IP table for port Ethernet #8.
Management and wayside ports
You only need to configure traffic enabled ports.
You dont need to configure the IP tables of management and wayside
ports that will not be included in a service path.
5.7.2.3 Examples
Example#1, Ethernet peer in XPAND IP+ nodal
In the configuration depicted below, the IP-table of Ethernet port#1, slots
1 and 2 must both be configured as shown.
HighCapNMS

IP Table for an XPAND IP+ unit Example#1
Nodal Mode, 2 Slots with Ethernet Cable Between Ports

Example#2, Ethernet peer in single pipe mode
HighCapNMS

IP Table for an XPAND IP+ Unit Example #2
Single Pipe Mode with Ethernet Peer

5.7.3 Peer Port Configuration
Unless LLDP is enabled in both sides in the elements IP table parameters must
be configured for an Ethernet service:
Peer IP address
Peer slot number
Peer port number
You must configure both ends of the Ethernet cable, and the configuration
must be symmetric.
For 1+1 HSB nodes, the configuration is done only for the active slot.
5.7.3.1 Peer IP Address
The Peer IP address parameter should be configured as the management IP
address of the network element owning the peer port.
If the peer is a port in any slot of a nodal network element:
If slots 1 and 2 are not protected:
Use the IP address of the network element (slot 1as the Peer IP address.
If slots 1 and 2 are protected:
If there is no floating IP address for the network element, use the IP
address of slot 1 as the Peer IP address.
HighCapNMS

If the network element uses a floating IP address, use the floating IP
address as the Peer IP address.
If the peer is a port in a network element with an external protection cable
between two XPAND IP+ units:
If the peer network element has not yet been configured as part of a
service, use the IP address of any XPAND IP+ units in the network
elements as the Peer IP address. It doesnt matter if the selected unit is
active or standby. Use this IP address as the Peer IP address for all the
peers on the network element.
For Nodal 2+2 protection:
Select one the IP addresses as the Peer IP address for all the peers on the
network element.
5.7.3.2 Peer Slot Number
This parameter should be configured to the peer slot number.
If the peer network element is a standalone XPAND IP+, the Slot ID should be
configured as a standalone slot ID, with the value of 0.
If the peer network element is a nodal XPAND IP+, the Slot ID should be
configured as a nodal appropriate slot ID, with the value between 1 and 6.
If the peer is nodal XPAND IP+ with hot standby protection:
With hot standby protection configured between slot #1 & slot#2, the peer
slot ID should be configured to #1, regardless of the active / standby state.
If the peer is hot standby external protected, the Slot ID should be configured
as a standalone slot ID, with the value of 0.
5.7.3.3 Peer Port Number
This parameter should be configured to the peer network element port
number.
As a default, the peer port number is the number of the peer port, between 1
and 7.
For LAG ports, the required configuration is the actual physical connection
between physical ports, unless using a 1+1 HSB configuration.
HighCapNMS

Example#3, LAG Ports
IP Table, Peer Port Configuration

5.7.3.4 Exceptions
If the LAG peer is hot standby protection (either in nodal or using external
protection)
The same port and slot should be configured as peer for both LAG ports.
Logical LAG port number (i.e LAG#1,LAG#2, LAG#3would be configured as
peer port of both active and standby XPAND IP+ and nodal slots.
IP table, Peer Port Configuration, LAG to Hot-Standby Connectivity Case

HighCapNMS

5.7.3.5 Examples
IP table, peer configuration, example #1

HighCapNMS

IP Table, IP Table Peer Port Configuration for LAG Ports, Example #2

5.7.4 Ethernet Ports Table Configuration
Configuration parameters for all network element ports, including LAG ports
are stored in the Ports table.
Port attributes that much be configured for an Ethernet service:
Port admin
Port type
Port service type
5.7.4.1 Port Admin
Port Admin must be configured by the user through the Web EMS GUI.
HighCapNMS does not support configuration of port admin parameter, nor
does it make changes to the port admin setting when provisioning an Ethernet
service.
It is users responsibility to make sure that all Ethernet ports traversed by the
service are enabled - not just the ports on the target SAPs.
Port Admin possible values:
Enabled
Disabled
HighCapNMS

5.7.4.2 Port Type
Port type must be configured by the user through the Web EMS GUI.
HighCapNMS does not support configuration of port type.
Port type possible values:
Trunk - Applicable in managed switch application, C-VLAN tagged
Access - Applicable in managed switch application, untagged.
Hybrid - Applicable in managed switch, pipe Ethernet applications, no
impact on VLAN
Customer network - Applicable in metro switch application, C- VLAN
tagged.
Provider network - Applicable in metro switch application, S- VLAN
tagged.
5.7.4.3 Port Service Type
Port service type is a new parameter added to XPAND IP+ in version I6.7.
Port service type possible values:
Service Access Point (SAP Port functions as an end point of services.
Service Network Point (SNP) Port functions as a middle point of services
Port service type must be configured by the user through the Web EMS GUI.
HighCapNMS does not support configuration of Port service type.
However, HighCapNMS might attempt to change this value while provisioning
a new service.
Port Service Type, EMS Configuration Window

HighCapNMS

HighCapNMS uses the port service type extensively in the two following
cases:
When checking services correct configuration
When HighCapNMS re-builds a service, if the SAPs of the service are
in ports that are not configured as SAPs, HighCapNMS will display this
service as misconfigured.
When suggesting SAPs for a new service.
A port configured as SNP could still be a candidate SAP provided it has
no services passing through. If the SNP is used as a SAP in the new
service, HighCapNMS will change the value of the Port Service Type to
SAP.
Upgrading network elements to I6.7
The Port Service Type is a new parameter that does not exist in previous
versions of XPAND IP+ (6.6.1 and below).
When upgrading a network element from a previous version to I6.7, the
service port type value will be added automatically and set to SNP for all
ports.
It is the users responsibility to change this value to SAP for any ports that are
already defined as existing service end points.
If the network element was configured as a SAP prior to the upgrade, the
service will be displayed as misconfigured until the service port type value is
reset to SAP.
HighCapNMS

6. HighCapNMS Network Support
6.1 Supported Protocols
SNMP V1 / V2C / V3
CLI / SSH-2
HTTP / HTTPS
FTP / SFTP
6.2 Port List
Optional means that the port may be blocked if the service it supplies is not
needed.
Configurable means that the port number may be configured. Note that if you
change a port number of the server, you should make sure that the client that
accesses that server also uses the same port number.
6.2.1 Ports Used for Sending from HighCapNMS Server
Port Number Protocol Packet Structure Details
161 SNMP UDP Sending SNMP Requests to
the network elements
162
Configurable SNMP (traps) UDP Sending SNMP traps
forwarding.
Optional
25 SMTP (mail) TCP To send HighCapNMS reports
& triggers by email.
Optional
69 TFTP UDP To upload/download
configuration files. Optional
80 HTTP TCP To manage XPAND IP+
devices
443 HTTPS TCP To manage XPAND IP+
devices
Optional
From 21 port to any
remote port (>1023)
FTP Control Port TCP To download software and
configuration files.
(FTP Server responds to
client's control port)

Optional
HighCapNMS

From Any port (>1023to
any remote port (>1023)

FTP Server random port
range can be limited
according to needed
configuration (number of
parallel configuration
uploads).
FTP Data Port TCP To download software and
(FTP Server sends ACKs
(and datato client's data
port)

Optional
6.2.2 Ports Used for Receiving to HighCapNMS Server
161 SNMP UDP
Sending SNMP Requests to
162
Configurable
SNMP (traps) UDP
Sending SNMP traps
forwarding.
Optional
25 SMTP (mail) TCP
To send HighCapNMS reports
& triggers by email.
Optional
69 TFTP UDP
To upload/download
80 HTTP TCP
To manage XPAND IP+
devices
443 HTTPS TCP
To manage XPAND IP+
devices
Optional
From 21 port to any
remote port (>1023)
FTP Control Port TCP
To download software and
(FTP Server responds to
client's control port)
Optional
HighCapNMS

From Any port (>1023) to
any remote port (>1023)
according to needed
uploads).
FTP Data Port TCP
To download software and
(FTP Server sends ACKs (and
data) to client's data port)
Optional

Port Number Protocol
Packet
Structure
Details
162
Configurable
SNMP (traps) UDP Recieve SNMP traps from network elements
1610 SNMP UDP Recieve SNMP traps from NBI

4001
Configurable
Propriety TCP HighCapNMS Client Server
Used for connected clients
and the redundant
Standby server.

69 TFTP UDP To download software and files.
Optional
21 FTP Control
Port
TCP To download software and configuration files.
(FTP client initiates a connection)
Optional
To any port (>1023from
any Port (>1023)

according to needed
uploads).
FTP Data
Port
TCP To download software and configuration files.
(FTP Client initiates data
connection to random port
specified by server)

Optional

9205
Configurable
Propriety TCP User Actions Logger server. Optional
HighCapNMS

Port Number Protocol
Packet
Structure
Details

9207
Configurable
Propriety TCP VarioManager Proxy Optional

HighCapNMS

6.2.3 Ports Used for Sending from VarioManager
161 SNMP UDP Sending SNMP requests to
69 TFTP UDP To upload/download
9205
Configurable
Propriety TCP User Actions Logger server.
Optional

9207
Configurable
Propriety TCP VarioManager Proxy.
Optional

9106
Configurable
Propriety TCP VarioManager security
server. the security server
can run locally. Optional
6.2.4 Ports Used for Receiving to VarioManager
69 TFTP UDP To download software files.
Optional
9106
Configurable
Propriety TCP VarioManager security
server. the security server
can run locally. Optional
6.2.5 Ports Used for Sending from the Web Based EMS
80 HTTP TCP To manage device
443 HTTPS TCP To manage device. Optional
6.2.6 Ports Used for Receiving to the Web Based EMS
21 FTP TCP To download software files.
Optional
Data port FTP TCP To download software files.
Optional
In addition (optional), for telnet access to the network element, open TCP port
23. For SSH access to the network element, open TCP port 22.
HighCapNMS

7. HighCapNMS License Information
7.1 Introduction
Licensed based scalability allows you to add features and capacity as needed.
When the user installs the HighCapNMS server for the first time, it is installed
with a demo license that will enable 30 days of work with all features
enabled, and no limitation on the number of managed NEs.
To manage more than 20 NEs, an additional license should be purchased.
HighCapNMS software is available on a CD that will be delivered to the client,
or downloaded via customer support.
A network element is counted according to the number of IDUs.
For example:
XPAND IP+ R2 with 6 slots is counted as 6 in the license.
7.2 License Requirements
Description Model #
Quantity per
server
Quantity for redundant servers
solution
HighCapNMS Software
+ License for 20 network
elements
HighCapNMS NMS 1 2
License for 21-100
network elements, per
NE
PV_21-100_NE 80 160
License for 101-500
network elements: per
NE
PV_101-500_NE 30 60
License for redundant
HighCapNMS support
PV_Redundant_Support 1 2
TDM trails PV_TDM_Provisioning 1 2
Ethernet services PV_Ethernet_Provisioning 1 2
mySQL Enterprise
Server 5.1
MySQL-License-PV 1 2
HighCapNMS

7.3 License Components
HighCapNMS uses a capacity based licensing system.
The built-in license can manage up to 20 elements. Additional licenses can be
purchased to align with the size and needs of network. Customers should
purchase the HighCapNMS software and the appropriate license based on the
number of managed network elements (number of IDUs).
The following license components are limited, based on the purchase order.
Feature Description
Managed network element limit Limits the number of managed elements (number IDUs). There is
no limit on the number of groups or symbols the user can add.
Feature set and enabled features Limits the features enabled by HighCapNMS. Two feature sets
are currently defined (default is Pro):
Pro All features are enabled, except the following which require a
specific license.
Enabled features Specific proposal for the following features that require a specific
license:
NSN NetAct interface
Redundant server support
End to end TDM trails provisioning
Ethernet services
Expiry date No expiry (permanent license), or expiry date of license (for
trials/demos)
7.3.1 Redundancy Server Support
Redundancy servers requires the same license including Redundancy in both
primary and secondary server.
7.3.2 TDM Trail License Requirements
The TDM service requires an additional license. When the license isnt
detected, users will not be able to create new TDM trails, view or edit TDM
trail lists, modify trail properties, or access TDM trail performance reports. In
addition, in the absence of a valid TDM trail license, trail alarms will not be
raised.
7.3.3 Ethernet Services License Requirements
Ethernet services require an additional license. When the license isnt
detected, users will not be able to create new EVC, view or edit EVC, modify
EVC properties, or access

HighCapNMS

7.4 Licensing MySQL
MySQL is provided as part of the HighCapNMS installation package, but comes
with its own license, which must be purchased separately.
HighCapRadio HighCapNMS SW uses internal MySQL SW database. The
following Item should be purchased on every new server HW.
Marketing model Item description Part number
MYSQL-LICENSE MySQL software License for Windows/Unix
platform.
SL-0003-X
You must update your HighCapNMS dealer or distributer with details of every
upgraded server:
Customer details: Final customer, integrator, country, and region.
Server details: operating system and serial number.
License details: Host ID and maximum network elements included in the
license.
General details: Installed by, installation date, and any additional notes.
7.5 Temporary Demo License
When the user installs the HighCapNMS server for the first time, it is installed
with a demo license that will enable 30 days of work with all features
enabled, and no limitation on the number of managed NEs.
14 days of notification will be provided before the license expires. The
notification will appear upon each login to remind the customer to contact
HighCapRadio to obtain a permanent license.
If a permanent license was not obtained within 30 days, the demo license will
expire and the user will no longer be able to log in. An error message will
advise the customer to obtain a permanent license.
The demo license will be activated once per station. Uninstalling and
reinstalling the HighCapNMS software will not grant a new demo license.
7.6 Obtaining a Permanent License
To obtain a permanent HighCapNMS license:
1 Install HighCapNMS and restart the machine.
2 Start HighCapNMS Client and select Help > About.
3 Write down the Host ID number.
4 Contact HighCapRadio Networks customer support to report the Host ID
number and request your license file.
5 Activate the new license
Copy the license file that you receive from customer support to the
HighCapNMS/config directory
- Windows: \HighCapNMS\config
- Solaris: /opt/HighCapNMS/config
6 Restart the server.
7 Start HighCapNMS Client.
HighCapNMS

8 Select Help > About to confirm the updated license information.
A permanent HighCapNMS license will be issued when the relevant order is
processed by HighCapRadio, after HighCapNMS is installed on the customer
station.
Once an order is placed and processed, the customer must send the License
Request Form to Customer Support, with all the relevant information.
Customer Support will verify that the necessary information was provided,
and that the order was properly made. The license will then be generated and
emailed to the customer, together with license installation instructions.
An invoice will be issued when the license is generated.
7.7 License Configuration Recommendations
The basic software item consists a built-in license for 20 network elements
(NEs), meaning it can manage up to 20 managed elements.
To manage more than 20 NEs, additional licenses should be purchased.
Customers should purchase the HighCapNMS software and the appropriate
license based on the number of managed network elements (the number of
IDUs).
It is possible (and preferable) to order the NMS servers including the
HighCapNMS/HCR NMS SW installation as a package.
Description Model # Part #
HighCapNMS Software (Win/Unix+ License for 20 NEs HighCapNMS NMS SP-0028-x*
License for 21-100 NEs: per NE PV_21-100_NE SR-0038-0
License for 1001 or more NEs: per NE PV_>1000_NE SR-0041-0
SP-0028-x- whereby "x" represents the latest released version of HighCapNMS
7.8 License Configuration Examples
Management of 130 NEs
Description Model # Quantity
HighCapNMS Software + License for 20
NEs
HighCapNMS NMS 1
License for 21-100 NEs: per NE PV_21-100_NE 80
Upgrade of Existing License from 60 NEs to 130 NEs
HighCapNMS

Management of 130 NEs, Redundant Servers Configuration
Description Model #
Quantity per
server
Quantity for
redundant
servers solution
HighCapNMS
Software + License for
20 NEs
HighCapNMS NMS 1 2
License for 21-100
NEs: per NE
PV_21-100_NE 80 160
License for 101-500
NEs: per NE
PV_101-500_NE 30 60
License for redundant
HighCapNMS support
PV_Redundant_Support 1 2
HighCapNMS

8. Hardware Capacity Recommendations
Number of managed
network elements
Number of parallel
connected clients
Server (Processor) Memory Hard drive
Up to 5,000 network
elements
Up to 10 NMS Clients Oracle T3 (SPARC)
Dell PowerEdge T110 II
(Win2008 Server)
8G 300 GB
Up to 7,000 network
elements
Up to 20 NMS Clients Oracle T3 (SPARC) 16G 600 GB
Up to 7,000 network
elements
Up to 40 NMS Clients Oracle T3 (SPARC) 32G 600 GB

8.1 Unix Server Capacity Examples
UNIX servers are supplied with HighCapNMS NMS already installed.
HighCapNMS supports Solaris 10 operation system for Oracle T3 servers.
HighCapRadio doesnt support UNIX servers that were not purchased through
HighCapRadio and were not installed by HighCapRadio.
All NMS software licenses and MySQL database software should be purchased
separately.
Oracle server hardware is delivered with one year basic warranty.
HP server hardware is delivered with three years basic warranty.
Annual warranty extensions are available.
Number of
managed
network
elements
Number of
parallel
connected
clients
Server Memory Hard drive HighCapRadio Marketing Model
Up to 5,000
network
elements
Up to 10 NMS
clients
Oracle T3 8G 300 GB HighCap-SW&HW,Med,Solaris
Up to 7,000
network
elements
Up to 20 NMS
clients
Oracle T3 16G 600 GB HighCap-SW&HW,High,Solaris
Up to 7,000
network
elements
Up to 40 NMS
clients
Oracle T3 32G 600 GB HighCap-SW&HW,UltraHigh,Solaris

HighCapNMS

UNIX Server, Network Elements <5,000, up to 10 Clients
Marketing model Item description
HighCap-SW&HW,Med,Solaris
Oracle T3-1 HW, Solaris OS with basic HighCap Radio SW license (20
NEs).
Supported configuration - up to 5K NEs and up to 10 clients
HighCap-SW&HW,High,Solaris
NEs).

HighCap-SW&HW,UltraHigh,Solaris
NEs).

8.2 Windows Server Capacity Recommendations
Unlike UNIX servers, Windows PCs can be purchased separately from the with
HighCapNMS software. Installation can be done by the customer.
All NMS software licenses and MySQL database software should be purchased
separately.
Windows Server, Network Elements <5,000, up to 10 Clients
PV-Win-HW-Medium
Dell T110 II HW, Windows 2008 server OS
Windows PC, Network Elements <600, up to 3 clients
HighCapNMS can be installed on any up to date Windows PC with minimum
requirements of 2GB memory. Maximum of 2-3 parallel NMS clients usage is
recommended with this basic configuration.
HighCapNMS

9. Compatibility Matrix

IDU Version HighCapNMS Version
2.35w 6.01e N6.1g N6.5r N6.6.0.0.1 N6.6.0.0.2 N6.6.0.1.2 N6.6.1.5.1 N6.7.0.2.0 N6.8.0.1.0 N6.9.0.1.1 N7.0.0.1.0
Evolution
METRO
10B00 N N N N N N N N N Y Y Y
Evolution
XPAND
10B00 N N N N N N N N N Y Y Y
Evolution
XPAND IP
R4B00 N N N N N N N N N Y Y Y
R6A00 N N N N N N N N N N N Y
AGG-NODE-
N 1RU
7.0.0.0.0.76 N N N N N N N N N N N Y
AGG-NODE-
N 1RU
T7.2.0.0.0.30 N N N N N N N N N N N Y
AGG-NODE-
N 2RU
7.0.0.0.0.76 N N N N N N N N N N N Y
AGG-NODE-
N 2RU
T7.2.0.0.0.30 N N N N N N N N N N N Y
AODC-C 7.0.0.0.0 N N N N N N N N N N N Y

HighCapRadioNMS Installation Guide - N7.0.0.1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HighCapRadioNMS Installation Guide - N7.0.0.1.0

Uploaded by

Copyright:

Available Formats

HighCapNMS

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide

N7.0 Installation and Configuration Guide