Migrating Allot NetXplorer Server from

Windows to Linux (TS)

Reference Guide

April 2012
Revision 0.1

Document Number: DC-002866(A)

Notice
This document contains information proprietary to Gilat Satellite Networks Ltd. and its affiliates and may not be
reproduced in whole or in part without the express written consent of Gilat Satellite Networks Ltd. The disclosure by Gilat
Satellite Networks Ltd. of information contained herein does not constitute any license or authorization to use or disclose
the information, ideas or concepts presented. The contents of this document are subject to change without prior notice.
Contents
Chapter 1: Introduction ................................................................................................................ 3
Document Scope ............................................................................................................ 3
Intended Audience ......................................................................................................... 3
Overview ........................................................................................................................ 3
Related Links and Documentation .................................................................................. 4
Terminology.................................................................................................................... 5
Assumptions ................................................................................................................... 5
Limitations ...................................................................................................................... 5
Requirements ................................................................................................................. 6
Additional Gross Point Machine ................................................................................................. 6
RAM Capacity ............................................................................................................................ 6
Database Backup....................................................................................................................... 6
NetXplorer and NetEnforcer Upgrade ........................................................................................ 6

Chapter 2: Migration Process ...................................................................................................... 9

Procedure Overview ....................................................................................................... 9
Deleting NetEnforcer Configuration from Additional NetXplorer Server........................... 9
Changing Import Timer Settings ................................................................................... 12
Changing Import Timer Settings on NetXplorer Server ........................................................... 12
Changing Import Timer Settings on NetEnforcer AC-402/802 Machines ................................ 14
Changing Import Timer Settings on NetEnforcer AC-1400 Machines ..................................... 15
Verifying Protocol Pack Version.................................................................................... 15
Connecting Additional Gross Point Machine to Network ............................................... 17
Importing Main NetEnforcer Machine ........................................................................... 17
Changing Imported Hosts to Global Scope ................................................................... 19
Adding Backup NetEnforcer Machine to Network ......................................................... 20
Converting Long-Term Monitoring Service from Windows to Linux NetXplorer Server.. 22

Appendix A: Verifying RAM Capacity ........................................................................................ 23

Appendix B: Upgrading NetEnforcer to the Latest Software Version ..................................... 25

Appendix C: Rollback to Windows ............................................................................................ 27

April, 2012 i
Proprietary and Confidential
Chapter 1: Introduction

In This Chapter
Document Scope .............................................................................................................................. 3
Intended Audience ........................................................................................................................... 3
Overview .......................................................................................................................................... 3
Related Links and Documentation ................................................................................................... 4
Terminology ..................................................................................................................................... 5
Assumptions ..................................................................................................................................... 5
Limitations ........................................................................................................................................ 5
Requirements ................................................................................................................................... 6

Document Scope
Until recently, Gilat has been using Microsoft Windows OS platform for running the
Allot NetXplorer (NX) Server. While the Allot NetXplorer software memory and CPU
requirements kept increasing, Gilat's customers experienced problems in
co-operation of the new NetXplorer software versions and Windows OS platform.
Therefore, Gilat decided to use Linux platform with 8 GB RAM for running the Allot
NetXplorer (NX) Server. The selected Linux platform is the CentOS RedHat freeware.
This document describes the procedure of migrating the Allot NetXplorer (NX) Server
from Windows to Linux OS.

Intended Audience
This document is intended for Gilat Technical Support personnel.

Overview
For migrating from Windows to Linux OS platform, additional NetXplorer Server
machine is used (Gross Point).
 For a customer having Aspen Hill machine (see Terminology on page 5), a Gross
Point machine (see Terminology on page 5) should be pre-ordered from Gilat (via
PM).
 For a customer having Gross Point machine, an additional Gross Point machine
should be taken from the local office for migration process only.
This machine, running the latest Kick-Start Image (Linux-based CentOS) without
NetEnforcer configurations, is set to operate in a customer’s network for performing
the migration process. The aim of the migration process is to create a database on
the new NetXplorer Server by importing a customer's machines and upgrade them.
At the end of the process, the database is copied from the additional NetXplorer
Server machine to the customer’s NetXplorer Server machine, and the customer's
machines resume their operation in the network.
The migration process at a customer's site results in an installed NetXplorer Server:

April, 2012 3
Proprietary and Confidential
Related Links and Documentation Introduction

 Based on Gross Point (or a newer module, if exists) hardware with 8 GB RAM.
 Running Linux CentOS, the latest NetXplorer and NetEnforcer software versions.

Figure 1: Decision Flow

Related Links and Documentation

 Latest Image for the NetXplorer Server can be found at:
ftp://techsupport:$giLat$@212.150.132.132/products/non baseband/allot
software versions/nx server/gross point hw (new)/
 Latest NetEnforcer version can be found at:
ftp://techsupport:$giLat$@212.150.132.132/products/non%20baseband/allot%2
0software%20versions/NE%20Server/

4 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
 Terminology

 Allot NetXplorer and Allot NetEnforcer Installation and Configuration Manual can
be found at:
ftp://techsupport:$giLat$@212.150.132.132/products/knowledgebase/qos/allot/
documents/gilat/techsupport/installtionandconfiguration/
 Latest Protocol Pack can be found at:
ftp://techsupport:$giLat$@212.150.132.132/products/KnowledgeBase/QOS/Allot
/Protocol_Packs/SwAndRN/

Terminology
Throughout this document, you will encounter the following terminology. Make sure
you understand what this terminology means.

Term Description
NetEnforcer (NE) Allot QoS device used by Gilat (402, 802, 1400, 502)
NetXplorer (NX) Allot QoS Server software that manages NetEnforcer
device
Aspen Hill Intel Server used in the past for QoS NMS
(P/N – 549120 Ver:31) Supports up to 4 GB RAM is now EOL (End of Life)
Gross Point Intel Server, currently used for QoS NMS platform
(P/N - 549120 Ver:40) Supports up to 8 GB RAM

Assumptions
The migration procedure assumes the following:
 Gross Point machines at customers' sites have been supplied with version 10.1 or
higher.
 If a customer uses Long-Term Monitoring service, Windows Server must be
upgraded to the latest NetXplorer Server software version (on page 25) for
copying the Long-Term database file.

Limitations
Migration from Windows to Linux OS implies the following limitations:
 Hardware characteristics of Aspen Hill Server ver: 31 (P/N – 549120) prohibit it
from migrating to Linux OS.

In such a case, the Aspen Hill machine must be replaced with a Gross Point
machine. For each customer with Aspen Hill hardware, contact the PM for
arranging the shipment of the Gross Point hardware.
Gilat PM group is aware of this requirement, and a formal announcement has
been made to allow this process.

April, 2012 5
Proprietary and Confidential
Requirements Introduction

 Migration from Allot AC-402/802 to AC-1400/502 must be performed by the Allot

Technical Support personnel only, due to changes in the database content type
(i.e., Enhanced Catalogs instead of Regular).

Requirements
Additional Gross Point Machine
Prior to the arrival to the customer’s site, an additional Gross Point machine must be
prepared.
The preparation includes creating:
 Image of the Linux CentOS (Kick-Start) - see Section Installing Kick-Start
Image on Allot NetXplorer Linux Server in Allot NetXplorer and Allot
NetEnforcer Installation and Configuration Manual, DC - 002556(X).
 The latest Allot NetXplorer Server version recommended by Gilat (on page 4)

TechSupport offices must order an additional Gross Point machine (P/N 529120,
ver. 40), in case they are missing the one.
IMEA office is recommended to send a used Gross Point machine from Gilat to
customers for the installation process only. For further information, please
contact the relevant PM / Technical Support PoC in Gilat Headquarters.

RAM Capacity
Take into consideration RAM capacity of a customer's Gross Point machine:
 If a customer already has a Gross Point machine, verify its RAM capacity (see
Verifying RAM Capacity on page 23).
 For a Gross Point machines with 4 GB RAM capacity, pre-order memory sticks
from Gilat (based on the P/N of the machine).

A customer’s NetXplorer Server memory must be increased to 8 GB.

Database Backup
Prior to installing the Linux Image, back up all databases running on the Windows
machine, as described in Section Backing Up Allot NetXplorer Server Database
in Allot NetXplorer and Allot NetEnforcer Installation and Configuration Manual,
DC - 002556(X).

NetXplorer and NetEnforcer Upgrade

Prior to upgrading Allot NetXplorer Server and NetEnforcer machines:

6 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
 Requirements

 Upgrading the NetEnforcer machine from version E8.1.X (or previous versions)
to version E9.1.4_B3 requires a new license key.

For license generation, contact the Technical

Support personnel in Gilat Headquarters.

 Upgrading the NetEnforcer machine to version 9.1.3 requires the Protocol Pack
3.8 (or higher) to be installed on the NetXplorer Server machine.
 Prior to converting the Long-Term monitoring service from Windows to Linux OS,
upgrade the Windows Server to the latest NetXplorer version.

April, 2012 7
Proprietary and Confidential
Chapter 2: Migration Process

In This Section
Procedure Overview......................................................................................................................... 9
Deleting NetEnforcer Configuration from Additional NetXplorer Server .......................................... 9
Changing Import Timer Settings .................................................................................................... 12
Verifying Protocol Pack Version ..................................................................................................... 15
Connecting Additional Gross Point Machine to Network ............................................................... 17
Importing Main NetEnforcer Machine ............................................................................................ 17
Changing Imported Hosts to Global Scope.................................................................................... 19
Adding Backup NetEnforcer Machine to Network .......................................................................... 20
Converting Long-Term Monitoring Service from Windows to Linux NetXplorer Server ................ 22

Procedure Overview
Perform the procedures in the following order:
1. Delete NetEnforcer configuration from additional NetXplorer Server (on page 9).
2. Change Import Timer Settings (on page 12).
3. Verify Protocol Pack Version (on page 15).
4. Connect an Additional Gross Point Machine to Network (on page 17).
5. Import Main NetEnforcer Machine (on page 17).
6. Change Imported Hosts to Global Scope (on page 19).
7. Add Backup NetEnforcer Machine to Network (on page 20).
8. Convert Long-Term Monitoring Service from Windows to Linux NetXplorer Server
(on page 22)

From this point onward, it is impossible to perform Rollback.

9. Install memory sticks on a customer’s NetXplorer machine.

10. Install the relevant Linux Image on a customer’s NetXplorer machine.
11. Copy the database from an additional NetXplorer Server to the customer’s
NetXplorer Server machine.
12. Connect the main NetXplorer Server machine to a network.

Deleting NetEnforcer Configuration from Additional

NetXplorer Server
After installing the Linux image on the additional NetXplorer Server, the default
database is configured with two NetEnforcer machines. Prior to importing customer's

April, 2012 9
Proprietary and Confidential
Deleting NetEnforcer Configuration from Additional NetXplorer Server Migration Process

NetEnforcer machines, existing configuration on the NetEnforcer machine must be

removed.

At this stage, an additional NetXplorer Server must NOT be connected to the

network.

Use a Cross cable (between the Technical Support PC and NetXplorer Server) to
connect offline to the additional Linux NetXplorer Server.

To delete NetEnforcer machine with Linux Image:

1. Browse to the NetXplorer Server on 172.17.7.1 and launch the NetXplorer
application GUI.
2. Connect to the NetXplorer GUI using the following credentials:
 Username: admin
 Password: $SatCom$
3. On the navigation pane, expand the Network node, right-click the NS QoS
machine node and select Delete from the pop-up menu.

10 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
 Deleting NetEnforcer Configuration from Additional NetXplorer Server

Figure 2: Deleting NetEnforcer with Linux Image

The System Message is displayed.

Figure 3: System Message

April, 2012 11
Proprietary and Confidential
Changing Import Timer Settings Migration Process

4. Click Yes. The selected NetEnforcer machine is deleted.

Changing Import Timer Settings

The NetXplorer Server and the NetEnforcer machine have a default timer of 5
minutes. Once the timer expires, the import process is declared as Failed, and then
it is restarted again. To allow importing large databases to the NetXplorer Server,
the import timer settings must be changed to 15 minutes.

While changing the import timer on the NetEnforcer machine, the

Apache HTTP Server is restarted. This Server collects buckets for
traffic monitoring, and therefore a displayed graph may show a cutoff
for a few seconds.

Perform the following procedures:

 Changing Import Timer Settings on NetXplorer Server (on page 12).
 Changing Import Timer Settings on NetEnforcer AC-402/802 Machines
(on page 14).
OR
 Changing Import Timer Settings on NetEnforcer AC-1400 Machines (on page 15)

Changing Import Timer Settings on NetXplorer Server

To change the import timer settings on the NetXplorer Server:
1. Connect to the NetXplorer Linux Server GUI using the following.
 Username: root
 Password: $SatCom$
The Linux Interface screen is displayed:

12 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
 Changing Import Timer Settings

Figure 4: Linux Interface

2. On the desktop of the Linux Interface screen, double-click the Computer icon to
expand the file system opt Allot Netxplorer jboss-5.1.0.GA
server allot deploy folders.
3. In the deploy folder, right-click the transaction-jboss-beans.xml file and
select Text Editor to open the file.
4. Search for the <property name="transactionTimeout"\<300\>\/property\>
instance and replace it to <property
name="transactionTimeout"\<900\>\/property\>.
5. Save the modified file.
6. Close the file.
7. On the desktop of the Linux Interface screen, double-click the Computer icon to
expand the file system opt Allot Netxplorer conf folders.
8. Right-click the swKeeper.ini file and select Text Editor to open the file.
9. Search for the following instances under [tasks/java] to replace:
From:

April, 2012 13
Proprietary and Confidential
Changing Import Timer Settings Migration Process

name = java
location = /usr/java/jdk1.6.0_20/bin
args = -server -Xrs -Xms640m -Xmx1024m
-XX:PermSize=192m -XX:MaxPermSize=192m
-Djava.rmi.server.hostname=10.17.13.15 -Dremoting.bind_by_host=false
-Dsun.net.client.defaultConnectTimeout=300000
-Dsun.net.client.defaultReadTimeout=300000
-Djava.endorsed.dirs=/opt/allot/netxplorer/jboss-5.1.0.GA/lib/endors
ed -classpath
/opt/allot/netxplorer/jboss-5.1.0.GA/bin/run.jar:/usr/java/jdk1.6.0_
20/lib/tools.jar org.jboss.Main -c allot -b 0.0.0.0

To:
name = java
location = /usr/java/jdk1.6.0_20/bin
args = -server -Xrs -Xms640m -Xmx1024m
-XX:PermSize=192m -XX:MaxPermSize=192m
-Djava.rmi.server.hostname=10.17.13.15 -Dremoting.bind_by_host=false
-Dsun.net.client.defaultConnectTimeout=900000
-Dsun.net.client.defaultReadTimeout=900000
-Djava.endorsed.dirs=/opt/allot/netxplorer/jboss-5.1.0.GA/lib/endors
ed -classpath
/opt/allot/netxplorer/jboss-5.1.0.GA/bin/run.jar:/usr/java/jdk1.6.0_
20/lib/tools.jar org.jboss.Main -c allot -b 0.0.0.0

10. Restart the NetXplorer Server machine by typing the command reboot.

Changing Import Timer Settings on NetEnforcer AC-402/802 Machines

This process can be performed only for Allot NetEnforcer 402/802 machines.

To change the import timer settings on the NetEnforcer AC-402/802 machines:

1. Telnet to the NetEnforcer machine using the following:
 Username: root
 Password: Bagabu
2. On the command prompt, type cd /etc/apache/ to access the apache folder.
3. Type vi httpd.conf to change parameters in the configuration file (using the VI
Editor).

14 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
 Verifying Protocol Pack Version

Remember that the Search service is case-sensitive, while searching for the
word Timeout.

Figure 5: Search for Timeout

4. Type Timeout and click n until the following parameter is displayed:

Figure 6: Timeout Parameter

5. Using the VI Editor, change the Timeout value from 300 to 900.
6. Using the cursor keys move your mouse to the number 3.
7. Type r, and then type 9.
8. Press Esc.
9. Type:wq!, and then press Enter.
10. Restart Apache Server by typing the command /etc/rc.d/rc.httpd restart.

Changing Import Timer Settings on NetEnforcer AC-1400 Machines

A script is available to change the Import Timer settings on Allot AC-1400 machines.
To change the Import Timer settings on NetEnforcer AC-1400 machines:
1. Follow the link to download the script:
ftp://techsupport:$giLat$@212.150.132.132
/Products/KnowledgeBase/QOS/Allot/NetEnforcer/AC1400/Tools/AOS_Full_Export
_Timeout/
2. Copy the script to the NetEnforcer machine and run it.

Verifying Protocol Pack Version

A lower Protocol Pack version on the NetXplorer Server creates a Database error,
while importing a NetEnforcer machine. This is due to incompatibility of protocols
classification. If the NetXplorer Protocol Pack version is lower than the NetEnforcer
Protocol Pack version, the NetXplorer Protocol Pack must be upgraded to the latest
Protocol Pack version available.
To verify Protocol Pack version:

April, 2012 15
Proprietary and Confidential
Verifying Protocol Pack Version Migration Process

1. On the NetXplorer Linux GUI, right-click the Network node and select
Configuration from the pop-up menu.
2. Select the Protocol Updates tab.

Figure 7: Protocol Updates Tab

3. Verify the Protocol Pack version installed.

4. On the active Windows NetXplorer GUI, expand the Network node and
right-click the NS QoS (i.e., NetEnforcer machine) and select Configuration
from the pop-up menu.
5. Select the Identification & Key tab.

Figure 8: Identification & Key Tab

6. Verify the Protocol Pack version installed.

If the NetXplorer Server Protocol Pack version is lower than that of the
NetEnforcer machine, upgrade the Protocol Pack.

16 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
 Connecting Additional Gross Point Machine to Network

Connecting Additional Gross Point Machine to Network

This procedure may cause network interruption. Therefore, perform it in a

planned downtime period.

To connect an additional Gross Point machine to network:

1. Disconnect the Windows NetXplorer Server machine from network.
2. Connect the Linux NetXplorer Server machine to the network.
Both machines must have the same IP address 172.17.7.1.
3. Ping the NetXplorer Server machine to verify connectivity.

Since the NetXplorer Linux machine does not have any device configured, it
does not affect the active NetEnforcer machines.

Importing Main NetEnforcer Machine

This procedure explains how to import the database to the newly installed Linux
NetXplorer Server. This is to avoid corruption of the database by performing a
sequence of NetXplorer Server upgrades.

Importing the NetEnforcer brings up the Short-Term Collector and the

configuration only. For information on the Long-Term collection service, see
Section Converting Long-Term Monitoring Service from Windows to Linux
NetXplorer Server (on page 22).

To import the Main NetEnforcer machine:

1. On the navigation pane of the NetXplorer Server GUI, from the Tools menu,
select Import NetEnforcer.

April, 2012 17
Proprietary and Confidential
Importing Main NetEnforcer Machine Migration Process

Figure 9: Importing NetEnforcer

The NetEnforcer Properties - Import screen is displayed.

Figure 10: NetEnforcer Properties - Import Screen

2. In the NetEnforcer Properties - Import screen:

 Specify the NetEnforcer Name.
 Type the password: allot or $SatCom$.
 Type the IP Address of the NetEnforcer being imported.
 From the Collector drop-down list, select <System Defined>.
3. Click Save.

18 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
 Changing Imported Hosts to Global Scope

4. In the pop-up window, click Allow to allow import to all catalogs.

5. Upon a successful import, the Import Device Results message is displayed.
This window lists all the catalogs and policies imported from the device.

Figure 11: Import Device Results

6. Wait up to five minutes before proceeding to step 7 to enable complete and

correct import of all catalogs.
7. Click Close.
8. Verify that all hosts and catalogs have been imported.
9. Change the imported hosts to global scope (on page 19).

Changing Imported Hosts to Global Scope

After the import, all the catalogs belong only to the machine that has been imported
and cannot be used by the redundant machine.
To enable catalogs to be used by both machines:
1. Connect to the NetXplorer Server using SSH.
2. Search for the host_convert.sh file that was uploaded as part of the Linux
Image post-installation process.
3. Type chmod 777 host_convert.sh for setting the file permissions.
4. Type dos2unix host_convert.sh. This command arranges the files' order that
has been corrupted during the host_convert.sh file upload to Linux.

April, 2012 19
Proprietary and Confidential
Adding Backup NetEnforcer Machine to Network Migration Process

Figure 12: Arranging Files Order

5. Type ./host_convert.sh to run an example shown below:

Figure 13: Example of Converting Hosts

6. When prompted for the device ID, use the ID from the line above.

Adding Backup NetEnforcer Machine to Network

After configuring the main NetEnforcer machine and verifying that it is operational,
the backup NetEnforcer machine must be added to operation. The backup
NetEnforcer machine is created on the NetXplorer Server GUI and is cleaned from
any configuration. It takes configuration from the main NetEnforcer machine by
performing the policy distribution action. This is done to prevent the duplication of
catalogs and policies.
To add a backup NetEnforcer machine to network:
1. On the NetXplorer Server GUI, from the Actions menu, select New
NetEnforcer.

Figure 14: Adding New NetEnforcer

2. In the New NetEnforcer window, specify the NetEnforcer machine's parameters,

as described in Section Importing Main NetEnforcer Machine (on page 17).
3. Click Save.

20 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
 Converting Long-Term Monitoring Service from Windows to Linux NetXplorer Server

4. On the navigation pane, expand the Network node, right-click the main NS QoS
(i.e., NetEnforcer machine) and select Policy Distribution from the pop-up
menu. The Policy Distribution screen is displayed.

Figure 15: Policy Distribution Screen

The source NetEnforcer machine is the one mentioned on the top of the Policy
Distribution screen.
5. Select the NetEnforcer machine to distribute the policy to the backup machine.
6. Click Distribute.
The process may take a few minutes.

If the process fails, contact Technical Support personnel at Gilat Headquarters.

The Allot Technical Support assistance is required.

From this point onward, rollback to Windows (on page 27) cannot be performed.

April, 2012 21
Proprietary and Confidential
Converting Long-Term Monitoring Service from Windows to Linux NetXplorer Server Migration Process

Converting Long-Term Monitoring Service from Windows to

Linux NetXplorer Server
If the Long Term Monitoring service is not installed on the NetXplorer Server,
skip this procedure.

To convert the Long-Term monitoring service from Windows to Linux NetXplorer

Server:
1. Perform the actions described in Appendix M of Allot Installation and
Configuration manual (on page 4).
2. Open the graphs and verify normal system operation.

22 Migrating Allot NetXplorer Server from Windows to Linux (TS)

Proprietary and Confidential
Appendix A: Verifying RAM Capacity
To verify RAM capacity of a Gross Point machine:
1. Open an SSH connection to the NetXplorer Server.
2. On the command prompt, type the command top. The following screen is
displayed:

Figure 16: Verifying RAM Capacity

3. Verify the Mem [Memory] field statement. If it states 4 GB, the RAM capacity
should be added.

April, 2012 23
Proprietary and Confidential
Appendix B: Upgrading NetEnforcer to the Latest
Software Version
To upgrade the NetEnforcer machine to the latest software version:
1. Follow the below FTP link to download the latest NetEnforcer software version:
ftp://techsupport:$giLat$@212.150.132.132/Products/Non BaseBand/Allot
Software Versions/NE Server/
2. Perform the upgrade procedure as described in Allot NetXplorer and Allot
NetEnforcer Installation and Configuration Manual, DC - 002556(X).

April, 2012 25
Proprietary and Confidential
Appendix C: Rollback to Windows
Rollback to Windows can be performed as long as the NetXplorer Server NetEnforcer
machines have the same version, and there is no need to perform special
operations, other than connecting the Windows Server to the network.
To perform the rollback:
1. Verify that the Linux NetXplorer Server is disconnected.
2. Place the Windows NetXplorer Server back to operation.
3. Use the NetXplorer Server application GUI to verify that the graphs can be
opened and changes can be made.

In case a rollback is needed after Upgrading NetEnforcer to the Latest Software

Version (on page 25), contact Technical Support personnel at Gilat
Headquarters.

April, 2012 27
Proprietary and Confidential