Security Management Center (SMC) powered by …...8 Chapter 1 Using Stonesoft Documentation How to Use This Guide The Management Center Installation Guide is intended for the administrators

Stonesoft 5.4

Stonesoft Management Center Installation Guide

Management Center

Legal Information

End-User License AgreementThe use of the products described in these materials is subject to the then current end-user license agreement, which can be found at the Stonesoft website:www.stonesoft.com/en/support/eula.html

Third Party LicensesThe Stonesoft software includes several open source or third-party software packages. The appropriate software licensing information for those products at the Stonesoft website:www.stonesoft.com/en/support/third_party_licenses.html

U.S. Government AcquisitionsIf Licensee is acquiring the Software, including accompanying documentation on behalf of the U.S. Government, the following provisions apply. If the Software is supplied to the Department of Defense (“DoD”), the Software is subject to “Restricted Rights”, as that term is defined in the DOD Supplement to the Federal Acquisition Regulations (“DFAR”) in paragraph 252.227-7013(c) (1). If the Software is supplied to any unit or agency of the United States Government other than DOD, the Government’s rights in the Software will be as defined in paragraph 52.227-19(c) (2) of the Federal Acquisition Regulations (“FAR”). Use, duplication, reproduction or disclosure by the Government is subject to such restrictions or successor provisions.

Product Export RestrictionsThe products described in this document are subject to export control under the laws of Finland and the European Council Regulation (EC) N:o 1334/2000 of 22 June 2000 setting up a Community regime for the control of exports of dual-use items and technology (as amended). Thus, the export of this Stonesoft software in any manner is restricted and requires a license by the relevant authorities.

General Terms and Conditions of Support and Maintenance ServicesThe support and maintenance services for the products described in these materials are provided pursuant to the general terms for support and maintenance services and the related service description, which can be found at the Stonesoft website:www.stonesoft.com/en/support/view_support_offering/terms/

Replacement ServiceThe instructions for replacement service can be found at the Stonesoft website:www.stonesoft.com/en/support/view_support_offering/return_material_authorization/

Hardware WarrantyThe appliances described in these materials have a limited hardware warranty. The terms of the hardware warranty can be found at the Stonesoft website:www.stonesoft.com/en/support/view_support_offering/warranty_service/

Trademarks and PatentsThe products described in these materials are protected by one or more of the following European and US patents: European Patent Nos. 1065844, 1189410, 1231538, 1231754, 1259028, 1271283, 1289183, 1289202, 1304830, 1304849, 1313290, 1326393, 1361724, 1379037, and 1379046 and US Patent Nos. 6,650,621; 6,856,621; 6,912,200; 6,996,573; 7,099,284; 7,127,739; 7,130,266; 7,130,305; 7,146,421; 7,162,737; 7,234,166; 7,260,843; 7,280,540; 7,325,248; 7,360,242; 7,386,525; 7,406,534; 7,461,401; 7,573,823; 7,721,084; and 7,739,727 and may be protected by other EU, US, or other patents, or pending applications. Stonesoft, the Stonesoft logo and StoneGate, are all trademarks or registered trademarks of Stonesoft Corporation. All other trademarks or registered trademarks are property of their respective owners.

DisclaimerAlthough every precaution has been taken to prepare these materials, THESE MATERIALS ARE PROVIDED "AS-IS" and Stonesoft makes no warranty to the correctness of information and assumes no responsibility for errors, omissions, or resulting damages from the use of the information contained herein. All IP addresses in these materials were chosen at random and are used for illustrative purposes only.

Copyright © 2012 Stonesoft Corporation. All rights reserved. All specifications are subject to change.

Revision: SGMIG_20120911

2

www.stonesoft.com/en/support/eula.html

www.stonesoft.com/en/support/third_party_licenses.html

www.stonesoft.com/en/support/view_support_offering/terms/index.html

www.stonesoft.com/en/support/view_support_offering/return_material_authorization/index.html

www.stonesoft.com/en/support/view_support_offering/warranty_service/index.html

TABLE OF CONTENTS

INTRODUCTION

CHAPTER 1Using Stonesoft Documentation . . . . . . . . . . . . 7

How to Use This Guide . . . . . . . . . . . . . . . . . . 8Typographical Conventions . . . . . . . . . . . . . . 8

Documentation Available . . . . . . . . . . . . . . . . . 9Product Documentation. . . . . . . . . . . . . . . . . 9Support Documentation . . . . . . . . . . . . . . . . 10System Requirements. . . . . . . . . . . . . . . . . . 10Supported Features . . . . . . . . . . . . . . . . . . . 10

Contact Information . . . . . . . . . . . . . . . . . . . . 10Licensing Issues . . . . . . . . . . . . . . . . . . . . . 10Technical Support . . . . . . . . . . . . . . . . . . . . . 10Your Comments . . . . . . . . . . . . . . . . . . . . . . 10Other Queries. . . . . . . . . . . . . . . . . . . . . . . . 10

CHAPTER 2Planning the Management Center Installation . . 11

Stonesoft System Architecture. . . . . . . . . . . . . 12Overview to the Installation Procedure . . . . . . . 13Important to Know Before Installation . . . . . . . 13

Supported Platforms. . . . . . . . . . . . . . . . . . . 13Date and Time Settings . . . . . . . . . . . . . . . . 13Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Obtaining Installation Files . . . . . . . . . . . . . . . 14Downloading the Installation Files . . . . . . . . . 14Checking File Integrity . . . . . . . . . . . . . . . . . . 14Creating the Installation CD-ROM. . . . . . . . . . 14

Obtaining License Files . . . . . . . . . . . . . . . . . . 15

INSTALLING THE MANAGEMENT CENTER

CHAPTER 3Installing the Management Center . . . . . . . . . . 19

Getting Started with Management Center Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing on Linux . . . . . . . . . . . . . . . . . . . . 20Configuration Overview . . . . . . . . . . . . . . . . . 20

Installing Management Center Components . . . 21Installing a Management Server . . . . . . . . . . 23Installing a Log Server . . . . . . . . . . . . . . . . . 25Installing a Web Portal Server . . . . . . . . . . . . 26Installing an Authentication Server. . . . . . . . . 27

Installing in Demo Mode. . . . . . . . . . . . . . . . 28Finishing the Installation. . . . . . . . . . . . . . . . 29

Starting the Management Center After Installation 29Starting the Management Server. . . . . . . . . . 29Starting the Management Client . . . . . . . . . . 30Logging in to the Management Center . . . . . . 30Accepting the Management Server Certificate 31Installing Licenses . . . . . . . . . . . . . . . . . . . . 31Binding POL-Based Licenses to Servers. . . . . 33Starting the Log Server and Web Portal Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Starting Servers Manually. . . . . . . . . . . . . . . 34If the Log Server or Web Portal Server Fails to Start . . . . . . . . . . . . . . . . . . . . . . . . 35Generating Server Certificates . . . . . . . . . . . 35

After the Management Center is Installed . . . . 37Configuring Additional Management Servers . . 37

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installing Licenses for Additional Management Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Installing Additional Management Servers . . . 38Applying the Authentication Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . 40

Non-Graphical Installation . . . . . . . . . . . . . . . . 41

CHAPTER 4Distributing Management Clients through Web Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Getting Started with Web Start Distribution . . . 44Distributing Clients from the SMC Servers . . . . 44Distributing Clients from a Separate Server . . . 45Accessing the Web Start Clients . . . . . . . . . . . 46

CHAPTER 5Configuring NAT Addresses for Stonesoft Components . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuration Overview . . . . . . . . . . . . . . . . . . 48Configuration Overview . . . . . . . . . . . . . . . . . 49

Defining Locations . . . . . . . . . . . . . . . . . . . . . 49Adding SMC Server Contact Addresses . . . . . . 51Setting the Management Client’s Location . . . . 53

3Table of Contents

MAINTENANCE

CHAPTER 6Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Getting Started with Upgrading the Management Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuration Overview . . . . . . . . . . . . . . . . . 58Upgrading Licenses . . . . . . . . . . . . . . . . . . . . 59

Upgrading Licenses Under One Proof Code. . . 59Upgrading Licenses Under Multiple Proof Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Installing Licenses . . . . . . . . . . . . . . . . . . . . 61

Upgrading the Management Center . . . . . . . . . 62Synchronizing Management Databases . . . . . 64

CHAPTER 7Uninstalling the Management Center . . . . . . . . 65

Overview to Uninstalling the Management Center 66Uninstalling in Windows . . . . . . . . . . . . . . . . . 66Uninstalling in Linux . . . . . . . . . . . . . . . . . . . . 66

APPENDICES

APPENDIX ACommand Line Tools . . . . . . . . . . . . . . . . . . . . 69

Management Center Commands . . . . . . . . . . . 70Engine Commands . . . . . . . . . . . . . . . . . . . . . 80Server Pool Monitoring Agent Commands . . . . . 87

APPENDIX BDefault Communication Ports. . . . . . . . . . . . . . 89

Management Center Ports. . . . . . . . . . . . . . . . 90Security Engine Ports . . . . . . . . . . . . . . . . . . . 93

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

4 Table of Contents

5

INTRODUCTION

In this section:

Using Stonesoft Documentation - 7

Planning the Management Center Installation - 11

6

CHAPTER 1

USING STONESOFT DOCUMENTATION

This chapter describes how to use the Stonesoft Management Center Installation Guide and lists other available documentation. It also provides directions for obtaining technical support and giving feedback.

The following sections are included:

How to Use This Guide (page 8)Documentation Available (page 9)Contact Information (page 10)

7

How to Use This Guide

The Management Center Installation Guide is intended for the administrators who install the Stonesoft Management Center. It describes the installation step by step. The chapters in this guide are organized in the general order you should follow when installing the system.

Most tasks are explained using illustrations that include explanations on the steps you need to complete in each corresponding view in your own environment. The explanations that accompany the illustrations are numbered when the illustration contains more than one step for you to perform.

Typographical ConventionsThe following conventions are used throughout the documentation:

We use the following ways to indicate important or additional information:

Tip – Tips provide additional helpful information, such as alternative ways to complete steps.

Example Examples present a concrete scenario that clarifies the points made in the adjacent text.

Table 1.1 Typographical Conventions

Formatting Informative Uses

User Interface textText you see in the User Interface (buttons, menus, etc.) and any other interaction with the user interface are in bold-face.

References, termsCross-references and first use of acronyms and terms are in italics.

Command lineFile names, directories, and text displayed on the screen are monospaced.

User input User input on screen is in monospaced bold-face.

Command parameters Command parameter names are in monospaced italics.

Note – Notes prevent commonly-made mistakes by pointing out important points.

Caution – Cautions prevent breaches of security, information loss, or system downtime. Cautions always contain critical information that you must observe.

8 Chapter 1 Using Stonesoft Documentation

Documentation Available

Stonesoft documentation is divided into two main categories: Product Documentation and Support Documentation. Each Stonesoft product has a separate set of manuals.

Product DocumentationThe table below lists the available product documentation.

PDF guides are available at http://www.stonesoft.com/support/. The Administrator’s Guide, and the Reference Guides and Installation Guides for Stonesoft Management Center, Stonesoft Firewall/VPN, Stonesoft IPS, and Stonesoft Layer 2 Firewall are also available as PDFs on the Management Center CD-ROM.

Table 1.2 Product Documentation

Guide Description

Reference Guide

Explains the operation and features of Stonesoft comprehensively. Demonstrates the general workflow and provides example scenarios for each feature area. Available as separate guides for Stonesoft Management Center and Stonesoft Firewall/VPN, and as a combined guide for Stonesoft IPS and Stonesoft Layer 2 Firewall.

Installation Guide

Instructions for planning, installing, and upgrading a Stonesoft system. Available as separate guides for Stonesoft Management Center and Stonesoft Firewall/VPN, and as a combined guide for Stonesoft IPS and Stonesoft Layer 2 Firewall.

Online Help

Describes how to configure and manage the system step-by-step. Accessible through the Help menu and by using the Help button or the F1 key in any window or dialog. Available in the Stonesoft Management Client and the Stonesoft Web Portal. An HTML-based system is available in the Stonesoft SSL VPN Administrator through help links and icons.

Administrator’s Guide

Describes how to configure and manage the system step-by-step. Available as a combined guide for Stonesoft Firewall/VPN, Stonesoft IPS, and Stonesoft Layer 2 Firewall, and as separate guides for Stonesoft SSL VPN and Stonesoft IPsec VPN Client.

User’s GuideInstructions for end-users. Available for the Stonesoft IPsec VPN Client and the Stonesoft Web Portal.

Appliance Installation GuideInstructions for physically installing and maintaining Stonesoft appliances (rack mounting, cabling, etc.). Available for all Stonesoft hardware appliances.

9Documentation Available

http://www.stonesoft.com/en/support/technical_support_and_documents/manuals/current/

Support DocumentationThe Stonesoft support documentation provides additional and late-breaking technical information. These technical documents support the Stonesoft guide books, for example, by giving further examples on specific configuration scenarios.

The latest Stonesoft technical documentation is available at the Stonesoft website athttp://www.stonesoft.com/support/.

System RequirementsThe system requirements for running the Stonesoft Management Center can be found in the Management Center Release Notes available at the Stonesoft Support Documentation pages.

Supported FeaturesNot all features are supported on all platforms. See the Appliance Software Support Table at the Stonesoft Support Documentation pages for more information.

Contact Information

For street addresses, phone numbers, and general information about Stonesoft products and Stonesoft Corporation, visit our website at http://www.stonesoft.com/.

Licensing IssuesYou can view your current licenses at the License Center section of the Stonesoft website at https://my.stonesoft.com/managelicense.do.

For license-related queries, e-mail [email protected].

Technical SupportStonesoft offers global technical support services for Stonesoft’s product families. For more information on technical support, visit the Support section at the Stonesoft website athttp://www.stonesoft.com/support/.

Your CommentsWe want to make our products fulfill your needs as well as possible. We are always pleased to receive any suggestions you may have for improvements.

• To comment on software and hardware products, e-mail [email protected].• To comment on the documentation, e-mail [email protected].

Other QueriesFor queries regarding other matters, e-mail [email protected].

10 Chapter 1 Using Stonesoft Documentation

http://www.stonesoft.com

mailto:[email protected]




https://my.stonesoft.com/managelicense.do

http://www.stonesoft.com/support/

https://my.stonesoft.com/support/search.do?product=StoneGate&search=appliance software support

https://my.stonesoft.com/support/search.do?product=StoneGate&search=StoneGate+Management+Center+&type=Release+Notes

https://my.stonesoft.com/support/document.do?product=StoneGate&docid=3927

http://www.stonesoft.com/support/

CHAPTER 2

PLANNING THE MANAGEMENT CENTER INSTALLATION

This chapter provides important information to take into account before the Stonesoft Management Center installation can begin. It also includes an overview to the installation process.


Stonesoft System Architecture (page 12)Overview to the Installation Procedure (page 13)Important to Know Before Installation (page 13)Obtaining Installation Files (page 14)Obtaining License Files (page 15)

11

Stonesoft System Architecture

The system consists of one or more Firewall/VPN, IPS, or Layer 2 Firewall engines, the Management Center, and Management Client(s). The Management Sever, Log Server, and one or more Management Clients are always included in the installation. The type and number of optional components and engines varies according to environment and depends on your licenses.

Illustration 2.1 Stonesoft System Architecture

The Management Center consists of the following standard components:

• The Management Server.• One or more Log Servers.

The Management Client is a single unified tool that is used for all configuration and monitoring tasks related to the whole system. You can install an unlimited number of Management Clients.

Optionally, and for a separate license fee, you can also have:

• One or more backup Management Servers.• One or more Web Portal Servers for Web Portal users.• One Authentication Server for end-user authentication.

The Management Center components can be installed separately on different machines or on the same machine, depending on your requirements.

The Management Center can manage several Security Engines. See the Management Center Reference Guide, Firewall/VPN Reference Guide, and the IPS and Layer 2 Firewall Reference Guide for general information on the Management Center and Security Engines.

Security Engines

Management Server

Log Server

Web Portal Server

Authentication Server

Management Client

Web Portal

12 Chapter 2 Planning the Management Center Installation

Overview to the Installation Procedure

1. Install and configure the Management Center and a Management Client. This is explained in Installing the Management Center (page 19).

2. (Optional) Set up Management Client distribution through Java Web Start for automatic installation and upgrade. This is explained in Distributing Management Clients through Web Start (page 43).

3. If network address translation (NAT) is applied to communications between system components, define Contact Addresses. This is explained in Configuring NAT Addresses for Stonesoft Components (page 47).

The chapters and sections of this guide proceed in the order outlined above.

Once you have installed the Management Center components and the Management Client, and configured the communications between the system components, you can proceed to configuring and installing the Firewall/VPN, IPS, and Layer 2 Firewall engines. See the Firewall/VPN Installation Guide, and the IPS and Layer 2 Firewall Installation Guide for information on installing the engines.

Important to Know Before Installation

Consult the Management Center Reference Guide, the Firewall/VPN Reference Guide, or the IPS and Layer 2 Firewall Reference Guide if you need more detailed background information on the operation of the system than what is offered in this chapter.

Supported PlatformsThe Release Notes list the basic requirements for installation. For information on supported and certified hardware, search for the version-specific Hardware Requirements in the technical documentation search at http://www.stonesoft.com/en/support/.

Date and Time SettingsMake sure that the Date, Time, and Time zone settings are correct on any computer you will use as a platform for any Management Center component, including the workstations used for the Management Client. The time settings of the engines do not need to be adjusted, as they are automatically synchronized to the Management Server’s time setting. For this operation, the time is converted to UTC time according to the Management Server’s time zone setting. The SMC always uses UTC internally.

Hosts FileDue to a restriction of the Java platform, the Management Server and Log Server hostnames must be resolvable on the computer running the Management Client (even if running on the same computer as the servers) to ensure good performance.

To ensure that the hostnames can be resolved, you can add the IP address-hostname pairs into the local hosts file on the client computer:

• In Linux: /etc/hosts • In Windows: \WINNT\system32\drivers\etc\hosts

13Overview to the Installation Procedure

http://www.stonesoft.com/en/support/

Obtaining Installation Files

Depending on your order, you may have received ready-made installation CD-ROMs for the Management Center. Otherwise, download the installation files from the Stonesoft website.

Downloading the Installation Files

To download the installation files1. Go to the Stonesoft Downloads page at https://my.stonesoft.com/download.

2. Enter your license code or log in using an existing user account.

3. Download the .iso image files or the installation .zip file.

Checking File IntegrityBefore installing the SMC from downloaded files, check that the installation files have not become corrupt or been modified. Using corrupt files may cause problems at any stage of the installation and use of the system. File integrity is checked by generating an MD5 or SHA-1 file checksum of the downloaded files and by comparing the checksum with the checksum on the download page at the Stonesoft website.

Windows does not have MD5 or SHA-1 checksum tools by default, but there are several third party programs available.

To check MD5 or SHA-1 file checksum1. Look up the correct checksum at https://my.stonesoft.com/download/.

2. Change to the directory that contains the file(s) to be checked.

3. Generate a checksum of the file using the command md5sum filename or sha1sumfilename, where filename is the name of the installation file.

4. Compare the displayed output to the checksum on the website. They must match.

Creating the Installation CD-ROMOnce you have checked the integrity of the installation files, create the installation CD-ROM from the files. Use a CD-burning application that can correctly read and burn the CD-structure stored in the .iso images. If the end result is a CD-ROM file with the original .iso file on it, the CD-ROM cannot be used for installation.

Caution – Do not use files that have invalid checksums. If downloading the files again does not help, contact Stonesoft technical support to resolve the issue.

What’s Next? If you downloaded the installation files as a .zip file, unzip the contents to the

installation location and proceed to creating Obtaining License Files (page 15). Otherwise, continue by Creating the Installation CD-ROM.


https://my.stonesoft.com/download/

https://my.stonesoft.com/download/

Obtaining License Files

You must generate license files and install them after the installation to bring your system fully operational. Each Management Server, Log Server, Web Portal Server, and Authentication Server must have its own license. However, a Management Server license that includes the high availability features is a combined license for all Management Servers and must list the IP addresses of all the Management Servers. The Authentication Server license defines the maximum number of RADIUS clients (excluding other Stonesoft components) that can use the authentication methods provided by the Authentication Server, and the maximum number of named users for user linking in the Authentication Server’s user database.

You must also generate and install licenses for any Firewall, IPS, Layer 2 Firewall and SSL VPN engines to be able to make them operational.

For more information on licenses, see the Administrator’s Guide.

To generate a new license1. Go to the License Center at www.stonesoft.com/license/.

2. Enter the required code (proof-of-license or proof-of-serial number) in the correct field andclick Submit. The license page opens.

3. Click Register. The license generation page opens.

4. Enter the IP addresses of the Management Center components you want to use.

5. Enter the Management Server’s proof-of-license code for the engines you want to license.•The Management Server’s proof-of-license can be found in the e-mail you received

detailing your licenses. Later, this information is shown in the Management Client for all licenses imported into the system.

6. Click Submit Request. The license file is sent to you in a moment. It will also becomeavailable for download at the license page.

All licenses include a maximum version on which they are valid. Automatic upgrade and installation of licenses is enabled by default. If you have disabled automatic license upgrades, you need to upgrade the licenses when you upgrade to a new major release of the software.

15Obtaining License Files

http://www.stonesoft.com/license/


INSTALLING THE

MANAGEMENT CENTER

In this section:

Installing the Management Center - 19

Distributing Management Clients through Web Start - 43

Configuring NAT Addresses for Stonesoft Components - 47

17

18

CHAPTER 3

INSTALLING THE MANAGEMENT CENTER

This chapter instructs how to install the Stonesoft Management Center on Windows and Linux platforms.


Getting Started with Management Center Installation (page 20)Installing Management Center Components (page 21)Starting the Management Center After Installation (page 29)After the Management Center is Installed (page 37)Configuring Additional Management Servers (page 37)Non-Graphical Installation (page 41)

19

Getting Started with Management Center Installation

You are ready to start the Management Center installation when you have obtained and verified the installation files. See Obtaining Installation Files (page 14) for more information on these tasks.

Log in to the system where you are installing the Management Center with the correct administrative rights. In Windows, you must log in with administrator rights. In Linux you must log in as root.

During the installation, certificates can be generated for the server components. The certificates are needed for authentication in establishing the secure encrypted communication channel between system components.

We recommend installing a Management Client on the system on which you install the Management Server. After this, further Management Clients can be installed locally by running the Management Center installer or be made available through Java Web Start (see Distributing Management Clients through Web Start (page 43)), which eliminates the need to update all Management Clients individually at each version upgrade. The Management Client has no configurable parameters.

Installing on LinuxThe installation creates sgadmin user and group accounts. If there is a pre-existing sgadmin account, the installation fails. All the shell scripts are owned by sgadmin and can be executed either by root or the sgadmin user. The shell scripts are executed with sgadmin privileges. After the installation, the sgadmin account is disabled. The sgadmin account is deleted at uninstallation.

Configuration Overview1. Install the Management Center. See Installing Management Center Components

(page 21). If you are installing on separate servers, install the Management Server as the first component.

2. Start the Management Center. See Starting the Management Center After Installation (page 29).

3. (Optional) Install additional Management Server(s). See Configuring Additional Management Servers (page 37).

Caution – Make sure that the operating system version you plan to install on is supported. The supported platforms for running the Management Center are listed in the Release Notes of the Management Center.

Caution – Do not install the Management Center on a Stonesoft appliance.

20 Chapter 3 Installing the Management Center

Installing Management Center Components

For obtaining, verifying, and preparing the installation files, see Obtaining Installation Files (page 14).

This section guides you through a Management Center installation in a graphical user interface. For command line installation in Linux, see Non-Graphical Installation (page 41).

To start the Installation1. Start the installation in one of the following ways:

•From a .zip file: unzip the file and run setup.exe on Windows or setup.sh on Linux.•From a CD-ROM: insert the installation CD-ROM and run the setup executable from the

CD-ROM:

2. When the Installation Wizard shows the Introduction screen, click Next to start theinstallation. The License Agreement appears.•You can click Cancel at any time to exit the installer.•You can click Previous at any time to go back.

3. Indicate that you agree to the license agreement and click Next.

Operating System Path to Executable

Windows 32 bit \Stonesoft_SW_Installer\Windows\setup.exe

Windows 64 bit \Stonesoft_SW_Installer\Windows-x64\setup.exe

Linux 32 bit /Stonesoft_SW_Installer/Linux/setup.sh

Linux 64 bit /Stonesoft_SW_Installer/Linux-x64/setup.sh

Note – If the CD-ROM is not automatically mounted in Linux, mount the CD-ROM with “mount /dev/cdrom /mnt/cdrom”.

21Installing Management Center Components

4. (Optional) Click Choose to browse to a different installation folder. This folder is for theapplication. Log Servers can have a separate data storage location.

5. Click Next.

6. Select where to create shortcuts. These shortcuts can be used to manually startcomponents and to run some maintenance tasks.

7. Click Next.

Note – We do not recommend selecting C:\Program Files\Stonesoft\Management Center as the installation directory in Windows. Selecting C:\Program Files\Stonesoft\Management Center as the installation directory creates an additional C:\ProgramData\Stonesoft\Management Center folder, which duplicates some of the folders in the installation directory. Some of the program data is also stored in the C:\ProgramData\Stonesoft\Management Center folder.

4


8. Select the installation type:•Typical installs all Management Center components except the Web Portal Server.•Management Client Only installation is meant for administrators’ workstations.•Demo Mode installation is meant for evaluating the SMC in a simulated environment.•Custom installation allows you to select components one by one.

9. Click Next.

10.(Custom installation only) Select the components that you want to install and click Next.

Installing a Management Server

To configure the Management Server installation1. Enter or select the Management Server’s IP address. The Management Server’s license

must be generated using this IP address.

2. Enter the IP address of the Log Server to which this Management Server sends its alerts.

3. Leave Install as a Service selected to make the Management Server start automatically.

Note – Make sure you have a license for any separately licensed components before installing them. The Web Portal Server and Authentication Server are not included in standard Management Center licenses.

What’s Next? For Demo Mode installations, proceed to Installing in Demo Mode (page 28). Otherwise, proceed to the next applicable section according to the components you are

installing:• Installing a Management Server.• Installing a Log Server (page 25).• Installing a Web Portal Server (page 26).• Installing an Authentication Server (page 27).

2


4. Click Next. You are prompted to create a superuser account.

5. Type in a User Name.

6. Enter and confirm the Password.

7. Click Next.

Note – This is the only account that can log in after the installation.

What’s Next? Proceed to the next applicable section according to the components you are installing:

• Installing a Log Server.• Installing a Web Portal Server (page 26).• Installing an Authentication Server (page 27).•Finishing the Installation (page 29).


Installing a Log Server

To configure the Log Server installation1. Enter or select the Log Server’s IP address. If IP address binding is used, the Log Server’s

license must be generated with this IP address as the binding.

2. Enter the IP address of the Management Server that controls this Log Server.

3. If the components are installed on different machines and the Management Server is notreachable at the moment, deselect Certify the Log Server during the Installation to avoidconnection attempts after installation. Certifying is mandatory for running the Log Server.

4. Leave Install as a Service selected to make the Log Server start automatically.

5. Click Next.

6. (Optional) Click Choose to browse to a different storage folder for log data. Remotelocations are not suitable for active storage, since quick and reliable access is required.

2

6


7. Click Next.

Installing a Web Portal Server

To configure the Web Portal Server installation1. Enter or select the Web Portal Server’s IP address. If IP address binding is used, the Web

Portal Server’s license must be generated with this IP address as the binding.

2. Enter the IP address for the Management Server that controls this Web Portal Server.

3. If the components are installed on different machines and the Web Portal Server is notreachable at the moment, deselect Certify the Web Portal Server during the Installationto avoid connection attempts after installation. Certifying is mandatory for running the WebPortal Server.

4. Enter the IP address of the Log Server to which this Web Portal Server sends its alerts.

5. Leave Install as a Service selected to make the Web Portal Server start automatically.

6. Click Next.


• Installing a Web Portal Server.• Installing an Authentication Server (page 27).•Finishing the Installation (page 29).

Note – Make sure you have a license for the Web Portal Server before installing it. The Web Portal Server is an optional component and is not included in standard Management Center licenses. You can use the Previous button to return to component selection.


• Installing an Authentication Server.•Finishing the Installation (page 29).

2


Installing an Authentication ServerMake sure you have a license for the Authentication Server before installing it. The Authentication Server is an optional component and is not included in standard Management Center licenses.

If you are installing a single node Authentication Server on a different computer than the Management Server, or installing an Authentication Server cluster, you must define the Authentication Server element and install the correct licenses in the Management Client before installing the Authentication Server node(s). See the section called Integrating Authentication Server Services in the Administrator’s Guide PDF or the Management Client Online Help.

To configure the Authentication Server installation1. Enter or select the Authentication Server’s IP address.

2. Enter the IP address of the Management Server that controls this Authentication Server.

3. If you are installing the components are installed on different machines and theManagement Server is not reachable at the moment, deselect Certify the AuthenticationServer during the Installation to avoid connection attempts after installation. Certifying ismandatory for running the Authentication Server and for installing the second node of acluster.

4. Enter the IP address of the Log Server to which this Authentication Server sends its alerts.

5. Leave Install as a Service selected to make the Authentication Server start automatically.

6. Click Next.

What’s Next? Proceed to Finishing the Installation (page 29).

2


Installing in Demo ModeThe Demo mode installation creates a simulated network environment for evaluation.

To install in Demo Mode1. Select the type of demo to install:

•Use a standard backup to simulate a preconfigured environment.•Select your own backup file to create the simulation based on your own backup.

2. (Custom backup file only) Click Choose and browse to the location of the backup file.

3. Click Next. A description of the Demo Mode installation is displayed.

4. Click Next. The Pre-Installation Summary is displayed.

5. Click Install. The installation starts.

6. When the installation finishes, click Next.

7. Click Done to close the installer. The Management Center starts up automatically in thebackground.

Note – Demo mode installation is for evaluation only. A Management Center in Demo mode cannot be used with any traffic inspection engines and cannot be upgraded.

What’s Next? The simulated environment is now ready for testing. Proceed to Logging in to the

Management Center (page 30).

2


Finishing the InstallationThis is the last chance to Cancel or make changes by clicking Previous.

To finish the installation1. Check that the information in the Pre-Installation Summary is correct and click Install to

install the selected components.•Depending on the options you selected, you may be prompted to generate certificates in

the course of the installation. If this happens, see the section To generate a certificate for an SMC server (page 35).

2. Click Done to close the installer.

Starting the Management Center After Installation

Proceed through the listed sections in order to start the Management Center for the first time:

1. Starting the Management Server.

2. Starting the Management Client.

3. Logging in to the Management Center (page 30).

4. Installing Licenses (page 31).

5. Binding POL-Based Licenses to Servers (page 33).

6. Starting the Log Server and Web Portal Server (page 34).

Starting the Management ServerIf the Management Server has been installed as a service, it should start automatically both after the installation and during the operating system boot process. In Windows, the Stonesoft Management Server service is controlled in the Services window, which can be found in the Windows Control Panel under the Administrative Tools category.

If the Management Server is installed as a service and has successfully started, proceed to Starting the Management Client. Otherwise, start the Management Server manually as explained below.

To start a Management Server that is not installed as a service• In Windows, use the shortcut icon in the location you selected during installation or run the

script <installation directory>/bin/sgStartMgtSrv.bat.• In Linux, run the script <installation directory>/bin/sgStartMgtSrv.sh.

Caution – If you are installing any server components as a service on a Windows system, make sure the Services window is closed before you proceed.

Note – If any Log Server, Web Portal Server, or Authentication Server certificate was not retrieved during the installation, a certificate must be retrieved manually before the server can be started. See To manually certify a Server (page 35).

29Starting the Management Center After Installation

Starting the Management Client

To start a locally-installed Management Client In Windows, use the shortcut icon in the location you selected during installation or run

the script <installation directory>/bin/sgClient.bat.

In Linux, run the script <installation directory>/bin/sgClient.sh. A graphical environment is needed for the Management Client.

Logging in to the Management CenterThe Management Client connects to the Management Server and to Log Servers. See Default Communication Ports (page 89) for a list of the ports used.

In Demo Mode, use the following credentials to log in to one of the default scenarios:

• User Name: demo• Password: demo• Server Address: 127.0.0.1

To log in to the Management Center1. Type in the user name and password for the Administrator you defined during the

Management Server installation.

2. Type in the Management Server’s IP address or DNS name. • If you connect to the Management Server from an external network, the Management

Server’s IP address may be translated using NAT.

3. Leave Remember Server Address selected if you want the Management Client to add theaddress permanently in the Server Address list.

4. Click Login.

Tip – You can access the Online Help system in the Login window or any other window in the Management Client by pressing the F1 key.

What’s Next? Logging in to the Management Center (page 30).


Accepting the Management Server CertificateA certificate dialog is displayed when the Management Client contacts any Management Server for the first time. As a precaution, you can ensure that the communication really is with your Management Server by checking the Certificate Authority fingerprint as explained below.

To check the Certificate Authority fingerprint1. View the Management Server fingerprint on the Management Server:

• In Windows, use the shortcut icon in the location you selected during installation (default: Start→Programs→Stonesoft Management Center→Show Fingerprint) or run the script <installation directory>/bin/sgShowFingerPrint.bat.

• In Linux, run the script <installation directory>/bin/sgShowFingerPrint.sh.

2. If the fingerprint matches, click Accept. The Management Client loads and opens.

Installing LicensesThe Management Center servers require licenses to become operational. To obtain licenses, see Obtaining License Files (page 15). You can install licenses even before the components are installed.

With no valid Management Server license, a notification is shown when you log in. If the message appears after licensing, make sure the licensed IP addresses are correct and active on the server when the Management Server service starts up.

To install licenses through the License Information message Click Continue and select the license file(s) in the dialog that opens.

To install licenses1. Select File→System Tools→Install Licenses. A file browser dialog opens.

2. Select the license files and click Install.

What’s Next? If the message is not shown, install the licenses as explained below. Otherwise, proceed to the section To check that the licenses were installed correctly.


To check that the licenses were installed correctly1. Click the Configuration icon and select Administration. The Administration Configuration

view opens.

2. Expand the Licenses branch and select All Licenses.

3. Check that all licenses you imported are listed here.

What’s Next? If you have Log Server or Web Portal Server licenses that are bound to the Management

Server’s POL code, proceed to Binding POL-Based Licenses to Servers. Otherwise, continue by Starting the Log Server and Web Portal Server (page 34).

1


Binding POL-Based Licenses to ServersYou must bind management-bound Log Server and Web Portal Server licenses to specific Log or Web Portal Servers. The licenses contain no IP address information to automatically bind them.

To bind a management-bound license to a Log or Web Portal Server1. Click the Configuration icon and select Administration. The Administration Configuration

view opens.

2. Browse to LicensesServers. Installed licenses appear in the right panel.

3. Right-click a management-bound license (a license that states Dynamic in place of an IPaddress) and select Bind. The Select License Binding dialog opens.

4. Select the correct server from the list.

1


5. Click Select. The license is now bound to the selected Log or Web Portal Server element.

If you made a mistake, you can still right-click the license and select Unbind.

Starting the Log Server and Web Portal ServerIf the Log Server and the Web Portal Server have been installed as a service, the servers are started automatically during the operating system boot process. However, if the operating system is rebooted and the servers do not yet have a license, you may need to start them as explained here.

• If you installed the Log Server or Web Portal Server as a service, you can start or stop the server manually in Windows through the Services window.

• In other cases, you can start the Log Server or Web Portal Server manually as explained in Starting Servers Manually.

Starting Servers ManuallyTo start the Log Server or Web Portal Server manually, run the scripts in a console window. Read the console messages for information on the progress. Closing the console stops the service.

To start the Log Server and Web Portal Server manually1. Start the Log Server:

• In Windows, use the shortcut icon in the location you selected during installation (default: Start→Programs→Stonesoft Management Center→Log Server) or run the script <installation directory>/bin/sgStartLogSrv.bat.

• In Linux, run the script <installation directory>/bin/sgStartLogSrv.sh.

2. If you have a Web Portal Server, start it in the same way:• In Windows, use the shortcut icon in the location you selected during installation (default:

Start→Programs→Stonesoft Management Center→Web Portal Server) or run the script <installation directory>/bin/sgStartWebPortalServer.bat.

• In Linux, run the script <installation directory>/bin/sgStartWebPortalServer.sh.

Note – The license is permanently bound to the Log or Web Portal Server when the server is started for the first time. Such licenses cannot be re-bound to some other Log or Web Portal Server without re-licensing or deleting the Log or Web Portal Server element it is bound to. Until you do that, the unbound license is shown as Retained.

What’s Next? If you have started all servers successfully, proceed to After the Management Center is

Installed (page 37). If you have trouble starting the server, see If the Log Server or Web Portal Server Fails to

Start.


If the Log Server or Web Portal Server Fails to StartIf the Log Server or Web Portal Server does not start automatically as a service.

1. Try starting the server manually as explained in the previous section to see if there is some error displayed on the console.

2. Check licenses are correctly bound to components as explained in To check that the licenses were installed correctly (page 32) and To bind a management-bound license to a Log or Web Portal Server (page 33).

3. Ensure that the server has a valid certificate for secure system communications. If there are certificate-related problems or problems you are not able to identify, try (re)generating the certificate as explained below.

Generating Server Certificates

To manually certify a Server• In Windows, run the <installation directory>/bin/sgCertifyLogSrv.bat or the <installation directory>/bin/sgCertifyWebPortalServer.bat script depending on server type.

• In Linux, run the <installation directory>/bin/sgCertifyLogSrv.sh or the <installation directory>/bin/sgCertifyWebPortalServer.sh script depending on server type.

To generate a certificate for an SMC server1. Enter the user name and password for the account you created during the Management

Server installation (other accounts with unrestricted permissions can also be used).

2. Click Accept to accept the certificate fingerprint of the Management Server’s CertificateAuthority. As a precaution, you can ensure that the communication really is with yourManagement Server as explained in To check the Certificate Authority fingerprint (page 31).The Server Selection dialog opens.

Note – If the Management Server is not running, see Starting the Management Server (page 29).


3. (Log Server or Web Portal Server only) Identify the component:• If the correct server is listed, select it.• If the correct server is not listed, select Create a New Log Server or Create a ne Web

Portal Server and enter a Name. This name is shown in the Management Client.

4. (Authentication Server only) Identify the component:• If the correct server is listed, select it.• If the correct server is not listed, select Create a New Authentication Server and enter a

Name. This name is shown in the Management Client.• If you are installing the second node of an existing Authentication Server, select Create a

new Authentication Server node in an existing cluster and select the Authentication Server where you want to add the node.


5. Click OK.

After the Management Center is Installed

• If you want to install an additional Management Server, proceed to Configuring Additional Management Servers (page 37).

• If you want to allow administrators to install Management Clients through Web Start, continue to Distributing Management Clients through Web Start (page 43).

• If NAT is applied to communications between any system components, proceed to Configuring NAT Addresses for Stonesoft Components (page 47).

• If you installed an Authentication Server, continue by Applying the Authentication Server Configuration (page 40).

• Otherwise, you are ready to configure the Firewall, IPS, and Layer 2 Firewall element(s) in the Management Client. The elements must be configured before installing the physical engines. See the Firewall/VPN Installation Guide and the IPS and Layer 2 Firewall Installation Guide for more information.

Configuring Additional Management Servers

This section guides you through an additional Management Center installation in a graphical user interface. For command line installation, see Non-Graphical Installation (page 41).

Only one Management Server at a time can be used for configuring and managing the system. Additional Management Servers act as hot standby servers for the active Management Server. You can use one to four additional Management Servers with one active Management Server. The configuration data stored on the active Management Server is automatically replicated to the additional Management Servers.

Overview1. If you have not yet installed a license for the additional Management Server, install the

license. See Installing Licenses for Additional Management Servers.

2. Install the additional Management Server using the Installation Wizard. See Installing Additional Management Servers.

What’s Next? Start the Log Server or Web Portal Server as described in Starting the Log Server and

Web Portal Server (page 34), then proceed to After the Management Center is Installed. The Authentication Server installation is complete. Proceed to After the Management

Center is Installed.

Caution – You must install and configure the Management Server that you want to use as the active Management Server before installing additional Management Server(s). See Installing a Management Server (page 23).

37After the Management Center is Installed

Installing Licenses for Additional Management ServersTo use additional Management Servers, you must have a special Management Server license that lists the IP addresses of all the Management Servers within the same SMC. You must install the license in the Management Client before installing the additional Management Server(s).

If you do not yet have the license, generate the license at the Stonesoft website after receiving the Proof-of-License (see Obtaining License Files (page 15)), and then install the license as described in Installing Licenses (page 31).

Installing Additional Management Servers

To install an additional Management Server1. Start the installation in one of the following ways:


CD-ROM:

2. Proceed according to the instructions in the Installation Wizard until you are prompted toselect which components you want to install.

3. If you also want to install a Log Server and a local Management Client on this computer,leave the Typical selected and click Next. Otherwise, select Custom, select thecomponents you want to install and click Next.

4. Select the IP address of the Management Server from the list or type it in.•This must be the IP address defined for the corresponding Management Server element.•The Management Server’s license must be generated using this IP address.

5. Type in the IP address of the Log Server for sending alerts.







Note – We do not recommend selecting C:\Program Files\Stonesoft\Management Center as the installation directory in Windows. Selecting C:\Program Files\Stonesoft\Management Center as the installation directory creates an additional C:\ProgramData\Stonesoft\Management Center folder, which duplicates some of the folders in the installation directory. Some of the program data is also stored in the C:\ProgramData\Stonesoft\Management Center folder.


6. Select Install as an Additional Management Server for High Availability.

7. Leave Install as a Service selected to make the Management Server start automatically.

8. Click Next and follow the instructions to start the installation. A login prompt forReplication opens.

9. Log in using an unrestricted administrator account. The Management Server Selectiondialog opens.

10.Select the correct Management Server from the list and click OK. The databases aresynchronized.

Repeat the steps above as necessary to install other additional Management Servers

Note – If the synchronization fails, run the sgOnlineReplication script on the additional Management Server when connectivity is restored.

8

39Configuring Additional Management Servers

If there is a Firewall between the first Management Server you installed and the additional Management Server(s), you must add rules that allow the communications between the servers when you define your Firewall Policy.

Applying the Authentication Server ConfigurationTo make the Authentication Server operational, you must apply the configuration.

To apply the Authentication Server configuration1. Expand Servers in the System Status view.

2. Right-click the Authentication Server and select Apply Configuration. A progress dialogopens.

What’s Next? If you want to allow administrators to install Management Clients through Web Start,

continue to Distributing Management Clients through Web Start (page 43). If NAT is applied to communications between any system components, proceed to

Configuring NAT Addresses for Stonesoft Components (page 47). Otherwise, you are ready to configure the Firewall, IPS, and Layer 2 Firewall element(s)

in the Management Client. The elements must be configured before installing the physical engines. See the Firewall/VPN Installation Guide and the IPS and Layer 2 Firewall Installation Guide for more information.

Note – If you are installing a cluster of Authentication Server nodes, apply the configuration only after creating and installing all nodes. Once the configuration has been applied to a single Authentication Server, the server cannot be converted into a cluster.


3. Click Close when the operation finishes.

Non-Graphical Installation

In Linux, the Management Center can also be installed on the command line. Before installing, check the installation package integrity using the MD5 or SHA-1 file checksums as explained in Checking File Integrity (page 14).

To begin the non-graphical installation1. Start the installation in one of the following ways:

•From a .zip file: unzip the file and run setup.sh.•From a CD-ROM: insert the installation CD-ROM and run the setup executable from the

CD-ROM:

2. Run the command “./setup.sh -nodisplay” (the “-nodisplay” switch can be omitted ifthere is no graphical environment running). The installer starts. You can use the followinggeneral commands at any point where the installer asks for your input:•Type “back” to return to the previous step.•Type “quit” to cancel the installation.

3. When prompted, press Enter to continue. The license agreement is displayed.

4. Press Enter to scroll through the license agreement and accept by typing “Y”. You areprompted to select the installation directory.

5. Press Enter to install to the default installation directory, or specify a different directory. Ifyou specify a different directory, you are prompted to confirm it.

6. You are prompted to select the link location for shortcuts to the most commonly usedcommand line tools.

7. Press Enter to create links in the default directory or select one of the other options. Areminder to verify the hosts file appears.

8. Press Enter to continue.

What’s Next? Continue the configuration of the Authentication Server in the Management Client. See

the Administrator’s Guide or the Management Client Online Help.

Note – You need a graphical environment to use the Management Client. It cannot be run on the command line. Only the server components can be run in a command line-only environment.





41Non-Graphical Installation

9. Select the components you want to install:•Press Enter to install all Management Center components except the Web Portal Server.•Press 2 to install only the Management Client.•Press 3 to install a simulated network environment for evaluation in Demo Mode.•Press 4 to install a different selection of components.

10.(Customized installation only) Enter the numbers of the components you want to select/deselect, separated by commas.•Entering the number of a selected component deselects it.•Entering the number of a component that is not selected selects it.•By default, the Management Server, Log Server, and Management Client are selected.•You can verify your selection by typing back in the next stage.

Example To install only the Web Portal Server, type 1,2,3,4 and press Enter.

The other installation options for the Management Center components are the same as in the graphical installation.


CHAPTER 4

DISTRIBUTING MANAGEMENT CLIENTS THROUGH WEB START

The Management Client can be distributed through Java Web Start. This eliminates the need for each administrator to upgrade their client when the SMC is upgraded to a new version (the version of the client must always match the version of the respective server).


Getting Started with Web Start Distribution (page 44)Distributing Clients from the SMC Servers (page 44)Distributing Clients from a Separate Server (page 45)Accessing the Web Start Clients (page 46)

43

Getting Started with Web Start Distribution

In addition to installing Management Clients through the Installation Wizard, you can also distribute them through Java Web Start. Management Clients distributed with Web Start have the same set of features as clients installed with the installation wizard, but when you upgrade, Web Start automatically downloads the new version when the user logs.

There are two ways to configure Web Start access:

• you can activate an internal Web server on the Management Server (the server distributes only Web Start clients). There is no need for manual installation or upgrade.

• you can use a separate web server or network drive for distributing the clients. You must install these files manually and perform a fresh installation at each SMC version upgrade.

Distributing Clients from the SMC Servers

To enable a Web Start server1. Click the System Status icon in the toolbar. The System Status view opens.

2. Expand Servers.

What’s Next? Distributing Clients from the SMC Servers. Distributing Clients from a Separate Server (page 45).

1

2

3

44 Chapter 4 Distributing Management Clients through Web Start

3. Right-click a Management Server and select Properties. The Properties dialog opens.

4. Switch to the Web Start tab.

5. Select Enable. The Web Start server options are enabled.

6. (Optional) Change the (TCP) Port Number that the Web Start Server uses. By default, thestandard HTTP port 80 is used on Windows and 8080 on Linux (which does not allow theuse of reserved ports for this type of service).

7. Click OK.

With these settings, the users can access the Web Start files at any addresses that the Management Server may have.

Distributing Clients from a Separate Server

If you do not want to use the Management Server as a Web Start server, you can place the Web Start package on a Web server.

The Web Start package can also be placed on a shared network drive. The path to the files, including the drive letter, must be the same for all administrators who use that particular version of the installation package. If the network drive paths vary, consider placing the package on a Web server instead.

To install the Web Start package1. Browse to Stonesoft_SW_Installer→Webstart on the installation CD-ROM.

2. Copy all files and all directories from the Webstart directory on the installation CD-ROM tothe directory where you want the Web Start files to be served.

Note – Make sure that the port is not used by other listening services on the server. For ports reserved for Stonesoft system services, see Default Communication Ports (page 89).

What’s Next? Test the client as explained in Accessing the Web Start Clients (page 46).

4

5

Note – You must delete the existing files and install a new Web Start package according to these instructions each time you upgrade the Management Center. Otherwise, any administrators who use Web Start-installed Management Clients are not able to log in.

Caution – The Web Start installation creates an index.html file in the installation directory. Any existing index.html file will be overwritten.

45Distributing Clients from a Separate Server

3. On the command line, change to the directory where the Web Start files are located on yourserver.

4. Run the Web Start setup script and give the URL or the path of the directory where the WebStart files are located on your server as the parameter:•Windows: cscript webstart_setup.vbs <web start directory>•Linux: run webstart_setup.sh <web start directory>

5. If necessary, modify the configuration of the Web server to return the appropriate MIMEtype for.jnlp files (application/x-java-jnlp-file). Consult the manual of your Webserver for instructions on how to configure the MIME type.

6. Delete the webstart_setup.vbs and webstart_setup.sh files from the directory.

Accessing the Web Start Clients

After configuration, the administrators can access the Management Client using the Web Start package. To be able to use the Web Start Management Client, there must be a current version of the Java Runtime Environment (JRE) installed (the version required is shown on the login page).

To access the Web Start Clients1. Enter the Web Start download page address in your Web browser

http://<server address>:<port>•:<port> is only needed if the server is configured to run on a different port from the HTTP

standard port 80.

2. Click the link for the Web Start client.•Web Start automatically checks if the version on the server is already installed on your

local computer. If not, the new client is automatically installed on your computer. This is done each time the client is started this way, automatically upgrading your client installation whenever needed without any action from you.

•The client starts and displays the login dialog.

3. Log in with your account credentials.

Table 4.1 Examples

Installation on Example Web Start Directory

Web server http://www.example.com/webstart/

Network drive file://localhost/c:/webstart/

What’s Next? If NAT is applied to communications between any system components, proceed to

Configuring NAT Addresses for Stonesoft Components (page 47). Otherwise, you are ready to configure the Firewall, IPS, and Layer 2 Firewall element(s)

in the Management Client. You must configure the elements before installing the physical engines. See the Firewall/VPN Installation Guide and the IPS and Layer 2 Firewall Installation Guide for more information.

46 Chapter 4 Distributing Management Clients through Web Start

CHAPTER 5

CONFIGURING NAT ADDRESSES FOR STONESOFT COMPONENTS

This chapter contains the steps needed to configure Locations and contact addresses when a NAT (network address translation) operation is applied to the communications between any of the system components.


Configuration Overview (page 48)Defining Locations (page 49)Adding SMC Server Contact Addresses (page 51)Setting the Management Client’s Location (page 53)

47

Configuration Overview

If there is network address translation (NAT) between communicating system components, the translated IP address may have to be defined for system communications. All communications between the system components are presented as a table in Default Communication Ports (page 89).

You use Location elements to configure system components for NAT. There is a Default Location to which all elements belong if you do not assign them a specific Location. If NAT is applied between two system components, you must separate them into different Locations and then add a contact address for the component that needs to be contacted.

You can define a Default contact address for contacting a system component (defined in the Properties dialog of the corresponding element). The component’s Default contact address is used in communications when system components that belong to another Location contact the component and the component has no contact address defined for their Location.

Illustration 5.1 An Example Scenario for Using Locations

In the example scenario above, the same Management Server and Log Server manage system components both at a company’s headquarters and in a branch office.

NAT could typically be applied at the following points:

• The firewall at the headquarters or an external router may provide the SMC servers external IP addresses on the Internet. The external addresses must be defined as contact addresses so that the system components at the branch offices can contact the servers across the Internet.

• The branch office firewall or an external router may provide external addresses for the system components at the branch office. Also in this case, the external IP addresses must be defined as contact addresses so that the Management Server can contact the components.

When contact addresses are needed, it may be enough to define a single new Location element, for example, for the branch office, and to group the system components at the branch office into the “Branch Office” Location. The same Location element could also be used to group together system components at any other branch office when they connect to the SMC servers at the headquarters.

To be able to view logs, the administrators at the branch office must select the “Branch Office” Location in the Management Client.

Internet

Headquarters Location Branch Office Location

Management/ Log Server

IPS IPSFirewall Firewall

Intranet Intranet

48 Chapter 5 Configuring NAT Addresses for Stonesoft Components

Configuration Overview1. Define Location element(s). See Defining Locations.

2. Define contact addresses for the Management Server, and Log Server(s). See Adding SMC Server Contact Addresses (page 51).

3. Select the correct Location for your Management Client. See Setting the Management Client’s Location (page 53).

4. Select the correct Location for Firewall, IPS, and Layer 2 Firewall engines when you create the engine elements. See the Firewall/VPN Installation Guide and IPS and Layer 2 Firewall Installation Guide.

Defining Locations

The first task is to group the system components into Location elements based on which components are on the same side of a NAT device. The elements that belong to the same Location element always use the primary IP address (defined in the main Properties dialog of the element) when contacting each other.

To create a new Location element1. Click the Configuration icon in the toolbar, and select Administration. The Administration

Configuration view opens.

1

49Defining Locations

2. Expand Other Elements.

3. Right-click Locations and select New Location. The Location Properties dialog opens.

4. Type in a Name.

5. Select all necessary element(s) and click Add.

6. Click OK.

Repeat to create other Locations as necessary.

2

3

5


Adding SMC Server Contact Addresses

The Management Server, Log Server, and Authentication Server can have more than one contact address for each Location. You must define two or more contact addresses per Location if you have additional Management Servers or Log Servers. Multiple contact addresses are required so that remote components can connect to a Management Server or a Log Server even if the active Management Server or Log Server fails. You must also define two or more contact addresses per Location if you have configured Multi-Link, so that remote components can connect to the server(s) even if a NetLink goes down.

To define Management Server and Log Server contact addresses1. Right-click a server and select Properties. The Properties dialog for that server opens.

2. Select the Location of this server.

What’s Next? If your Management Server or Log Server needs a contact address, proceed to Adding

SMC Server Contact Addresses (page 51). Otherwise, you are ready to configure the Firewall, IPS, and Layer 2 Firewall element(s)


1

2

3

51Adding SMC Server Contact Addresses

3. If necessary, enter additional Default contact address(es).•A default contact address is automatically entered based on the element properties.• If the server has multiple Default contact addresses, separate the addresses with

commas.• If necessary, the Exceptions button allows you to define other contact addresses for

specific Locations

4. Click OK.

Repeat to define the contact addresses for other servers as necessary.

To define Authentication Server contact addresses1. Right-click the Authentication Server and select Properties. The Authentication Server

properties open.

2. Select the node for which you want to define contact addresses and click Edit. The NodeProperties dialog opens.

3. Select the Location of this server.

4. If necessary, enter additional Default contact address(es).•A default contact address is automatically entered based on the element properties.• If the server has multiple Default contact addresses, separate the addresses with

commas.• If necessary, the Exceptions button allows you to define other contact addresses for

specific Locations.

Note – Elements that belong to the same Location element always use the primary IP address when contacting each other instead of any Contact Addresses. All elements not specifically put in a certain Location are treated as an additional Location.

2


5. Click OK.

Setting the Management Client’s Location

When NAT is performed between the Management Client and a Log Server, you must select the correct Location for your Management Client in the status bar at the bottom of the Management Client window to be able to view logs. You must select the Management Client location separately in each administrative Domain if there are multiple Domains in your environment.

To select the Management Client’s Location Click the Default Location name in the status bar at the bottom of the window and select

the correct Location.

Note – Elements that belong to the same Location element always use the primary IP address when contacting each other instead of any Contact Addresses. All elements not specifically put in a certain Location are treated as an additional Location.

What’s Next? If NAT is performed between your Management Client and a Log Server, proceed to

Setting the Management Client’s Location (page 53). Otherwise, you are ready to configure the Firewall, IPS, and Layer 2 Firewall element(s)


What’s Next? You are ready to configure Security Engine element(s). See the Firewall/VPN Installation

Guide and the IPS and Layer 2 Firewall Installation Guide for more information.

53Setting the Management Client’s Location


MAINTENANCE

In this section:

Upgrading - 57

Uninstalling the Management Center - 65

55

56

CHAPTER 6

UPGRADING

This chapter explains how you can upgrade the Stonesoft Management Center.


Getting Started with Upgrading the Management Center (page 58)Upgrading Licenses (page 59)Upgrading the Management Center (page 62)

57

Getting Started with Upgrading the Management Center

You can upgrade Management Center components without uninstalling the previous version. It is important to upgrade the Management Center components before upgrading the engines, because the old Management Center version may not be able to recognize the new version engines and generate a valid configuration for them. Many older versions of engines can be controlled by newer Management Center versions. See the Release Notes for possible version-specific restrictions.

The security engines do not require a continuous connection to the Management Center and they continue to operate normally during the Management Center upgrade. The engines temporarily store their logs locally if the Log Server is unavailable and then send them to the Log Server as it becomes available again.

For more detailed instructions, see the Management Client Online Help or the Administrator’s Guide PDF.

Before upgrading, read the Release Notes for the new version athttp://www.stonesoft.com/en/support/technical_support_and_documents.

Configuration Overview1. Obtain the installation files and check the installation file integrity as explained in

Downloading the Installation Files (page 14).

2. (If automatic license updates have been disabled) Update the licenses as explained in Upgrading Licenses (page 59).

3. Upgrade all Management Servers, Log Servers, and Web Portal Servers as explained in Upgrading the Management Center (page 62).

4. Upgrade any locally installed the Management Clients by running the Management Center installer and any Web Start distributions that are located on an external servers as explained in Distributing Clients from a Separate Server (page 45).

Caution – All the Management Center components (Management Server, Management Client, Log Server, the optional Web Portal Server, and the optional Authentication Server) must use the same software version to be able to work together. Plan ahead to perform all necessary upgrades.

What’s Next? If the current licenses are valid for the new version, proceed to Upgrading the

Management Center (page 62). Otherwise, continue by Upgrading Licenses (page 59).

58 Chapter 6 Upgrading

https://my.stonesoft.com/support/browse.do?product=StoneGate&browsetype=type&selection=Release+Notes

Upgrading Licenses

When you installed the SMC for the first time, you installed licenses that work with all versions up to that particular version. If the first two numbers in the old and the new version are the same, the upgrade can be done without upgrading licenses (for example, when upgrading from 1.2.3 to 1.2.4).

When either of the first two numbers in the old version and the new version are different, you must first upgrade your licenses (for example, when upgrading from 1.2.3 to 1.3.0). Automatic regeneration and installation of licenses is enabled by default. You can also upgrade the licenses at the Stonesoft website.

If you do not need to upgrade licenses, proceed to Upgrading the Management Center (page 62).

Upgrading Licenses Under One Proof Code

To upgrade a license1. Open a web browser and go to www.stonesoft.com/license

2. Enter the POL code in the License Identification field and click Submit. The license pageopens.

3. Click Update. The license upgrade page opens.

4. Follow the directions to upgrade the license.

What’s Next? Proceed to Upgrading Licenses Under One Proof Code to upgrade the licenses one by

one. Proceed to Upgrading Licenses Under Multiple Proof Codes (page 60) to upgrade

several licenses at once.

What’s Next? Repeat these steps for other licenses, then proceed to Installing Licenses (page 61).

59Upgrading Licenses

http://www.stonesoft.com/license/

Upgrading Licenses Under Multiple Proof CodesIf you have several existing licenses with different POL (proof-of-license) codes that you need to upgrade, you can make the work easier by generating the new licenses all at once.

To upgrade multiple licenses1. Click the Configuration icon and select Administration. The Administration Configuration

view opens.

2. Browse to Licenses→All Licenses. All the licenses appear in the right panel.

3. Ctrl-select or Shift-select the licenses you want to upgrade.

4. Right-click one of the selected items and select Export License Info. The LicenseRequest Browser dialog opens.

5. Save the license information file. A confirmation dialog opens.

6. Optional) Click Yes to launch the Stonesoft License Center website's multi-upgrade formin your default Web browser.

7. Upload the license upgrade request file to the Stonesoft License Center website using themulti-upgrade form.

1

3

6


You can view and download your current licenses at the license website (log in by entering the proof-of-license or proof-of-serial number code at the License Center main page).

Installing LicensesAfter you have upgraded the licenses as described above, you install the license file in the Management Client.

To install licenses1. Select File→System Tools→Install Licenses. A file selection dialog opens.

2. Select the license files and click Install.

3. Browse to Licenses→All Licenses in the Administration Configuration view.

4. Check that the licenses are now correctly upgraded to the new version. When you onlyupgrade the software version in the license, old licenses are automatically replaced.

3

61Upgrading Licenses

Upgrading the Management Center

There is no need to uninstall the previous version. Upgrading from all older versions may not be possible without an intermediate upgrade. See the Release Notes for more information.

It is possible to revert automatically to the previous installation if the Management Center upgrade fails for some reason. The installer can also back up of the Management Server configuration. For more information on backups (such as the steps for restoring), refer to the Online Help of the Management Client or the Administrator’s Guide PDF.

The same installer works with all Management Center components, including locally installed Management Clients.

If you have multiple Management Servers, you can upgrade them in any order. Management Servers are automatically isolated from database replication during the upgrade. There is no need to explicitly isolate the Management Servers before upgrading.

To upgrade Management Center components1. Start the upgrade in one of the following ways:


CD-ROM:

2. When the Installation Wizard shows the Introduction screen, click Next to start theupgrade. The License Agreement appears.

3. Indicate that you accept the License Agreement and click Next to continue the installation.








4. Make sure the installation directory is correct for your installation and click Next.•All installed components must be upgraded at the same time. You can install additional

components if you wish (see Installing the Management Center (page 19) for installation instructions).

5. (Management Server only, optional) Select Save Current Installation to save a copy of thecurrent installation that you can revert to at any time after the upgrade.

6. Click Next.

7. (Management Server and Authentication Server only) Select whether to back up the serverand click Next:•Select Yes to create a backup that can be used and viewed without a password. •Select Yes, encrypt the backup to create a password-protected backup. You are

prompted for the password as you confirm the selection.•Select No if you already have a recent backup of the Management Server or

Authentication Server.

5

63Upgrading the Management Center

8. Check that the information in the Pre-Installation Summary is correct and click Install. Theupgrade begins.

9. (Optional) When the upgrade is finished, follow the link(s) in the notification to launch thereport(s) of system changes in your Web browser before you exit the installer.

Synchronizing Management DatabasesYou must synchronize the configuration information between all Management Servers through the Management Client after upgrading the Management Servers.

To synchronize management databases1. Connect to the active Management Server using the Management Client.

2. Select File→System Tools→Control Management Servers. The Control ManagementServers dialog opens.

3. Right-click the additional Management Server and select Replication→Isolate. You areprompted to confirm the isolation.

4. Click Yes. The additional Management Server’s database is made incompatible with theActive Management Server’s database.

5. Click OK to acknowledge the completion of the isolation.

6. Right-click the isolated Management Server and select Replication→Full DatabaseSynchronization. You are prompted to confirm the synchronization.

7. Click Yes. All existing configurations on the isolated Management Server are overwritten.

8. Click OK to acknowledge the completion of the synchronization and wait for theManagement Server to restart.

9. If you need to synchronize more than one additional Management Server, repeat Step 3-Step 8 for each Management Server.

10.Click Close to close the Control Management Servers dialog.

Caution – If you are working on a Windows system and you are upgrading any SMC component that runs as a service, make sure the Services window is closed before you complete the next step. Otherwise, the service may not be installed correctly.

What’s Next? If you have multiple Management Servers, upgrade all of the Management Servers and

proceed to Synchronizing Management Databases. If administrators have Management Clients installed locally, upgrade the Management

Clients by running the same Management Center installer on those hosts. If you are distributing Web Start Management Clients from an external server, install a

new Web Start package in the same way as the original installation was made. See Distributing Management Clients through Web Start (page 43).

Otherwise, the Management Center upgrade is now complete. See the Firewall/VPN Installation Guide and IPS and Layer 2 Firewall Installation Guide if you are upgrading engines as well.


CHAPTER 7

UNINSTALLING THE MANAGEMENT CENTER

This chapter instructs how to uninstall the Management Center components.


Overview to Uninstalling the Management Center (page 66)Uninstalling in Windows (page 66)Uninstalling in Linux (page 66)

65

Overview to Uninstalling the Management Center

It is not possible to uninstall the Management Center components one by one. If you have several Management Center components installed on the same computer, all components are uninstalled. The sgadmin account is deleted during the uninstallation of the Management Center.

By default, the Management Center is installed in the following directories:

• Windows: C:\Stonesoft\Management Center• Linux: /usr/local/stonesoft/management_center

There is a .stonegate directory in each user’s home directory in the operating system, which contains the Management Client configuration files. These files are not automatically deleted but can be removed manually after the uninstallation.

Uninstalling in Windows

To uninstall in Windows1. Launch the uninstaller in one of the following ways:

•Open the list of installed programs through the Windows Control Panel, right-click Stonesoft Management Center, and select Uninstall/Change.

•Alternatively, run the script <installation directory>\uninstall\ uninstall.bat

2. When the uninstaller starts, click Uninstall. All Management Center components areuninstalled.

Uninstalling in Linux

To uninstall in graphical mode1. Stop the Management Center components on the machine.

2. Run the script <installation directory>/uninstall/uninstall.sh

3. When the uninstaller starts, click Uninstall. All Management Center components areuninstalled.

To uninstall in non-graphical mode1. Stop the Management Center components on the machine.

2. Run the script <installation directory>/uninstall/uninstall.sh -nodisplay

Note – Back up the Management Server and the Log Server before uninstalling the Management Center if you want to preserve the stored data.

66 Chapter 7 Uninstalling the Management Center

67

APPENDICES

In this section:

Command Line Tools - 69

Default Communication Ports - 89

Index - 97

68

APPENDIX A

COMMAND LINE TOOLS

This appendix describes the command line tools for Stonesoft Management Center and the engines.


Management Center Commands (page 70)Engine Commands (page 80)Server Pool Monitoring Agent Commands (page 87)

Note – Using the Management Client is the recommended configuration method, as most of the same tasks can be done through it.

69

Management Center Commands

Management Center commands include commands for the Management Server, Log Server, Web Portal Server, and Authentication Server. Most of the commands are found in the <installation directory>/bin/ directory. In Windows, the command line tools are *.bat script files. In Linux, the files are *.sh scripts.

Commands that require parameters must be run through the command line (cmd.exe in Windows). Commands that do not require parameters can alternatively be run through a graphical user interface, and may be added as shortcuts during installation.

Note – If you installed the Management Server in the C:\Program Files\Stonsoft\Management Center directory in Windows, some of the program data is stored in the C:\ProgramData\Stonesoft\Management Center directory. Command line tools may be found in the C:\Program Files\Stonsoft\Management Center\bin and/or the C:\ProgramData\Stonesoft\Management Center\bin directory.

Caution – login and password parameters are optional. Giving them as Command Line parameters may pose a security vulnerability. Do not enter login and password information unless explicitly prompted to do so by a Command Line tool.

70 Appendix A Command Line Tools

Table A.1 Management Center Command Line Tools

Command Description

sgArchiveExport

[host=<Management Server Address[\Domain]>] [login=<login name>] [pass=<password>] [format=<exporter format: CSV or XML>] i=<input files and/or directories>[o=<output file name>] [f=<filter file name>] [e=<filter expression>] [-h | -help | -?] [-v]

Displays or exports logs from archive. This command is only available on the Log Server. The operation checks privileges for the supplied administrator account from the Management Server to prevent unauthorized access to the logs.Enclose details in double quotes if they contain spaces.Host specifies the address of the Management Server. If the parameter is not defined, the loopback address (localhost) is used.login defines the username for the account that is used for this operation. If this parameter is not defined, the username root is used.pass defines the password for the user account.format defines the file format for the output file. If this parameter is not defined, the XML format is used.i defines the source from which the logs will be exported. Can be a folder or a file. The processing recurses into subfolders.o defines the destination file where the logs will be exported. If this parameter is not defined, the output is displayed on screen.f defines a file that contains the filtering criteria you want to use for filtering the log data. You can export log filters individually in the Management Client through Tools→Save for Command Line Tools in the filter’s right-click menu.e allows you to type in a filter expression manually (using the same syntax as exported filter files).-h, -help, or -? displays information on using the script.-v displays verbose output on the command execution.Example (exports logs from one full day to a file using a filter):sgArchiveExport login=admin pass=abc123i=c:/stonesoft/Stonesoft/data/archive/firewall/year2011/month12/./sgB.day01/ f=c:/stonesoft/Stonesoft/export/MyExportedFilter.flp format=CSV o=MyExportedLogs.csv

71Management Center Commands

sgBackupAuthSrv

[pwd=<password>][path=<destpath>][nodiskcheck][comment=<comment>][-h | --help]

Creates a backup of Authentication Server user information. The backup file is stored in the <installation directory>/backups/ directory. Backing up the Authentication only backs up Users, not the configuration of the Authentication Server. The Authentication Server configuration is included in the Management Server backup.pwd enables encryption.path defines the destination path.nodiskcheck ignores free disk check before creating the backup.comment allows you to enter a comment for the backup. The maximum length of a comment is 60 characters.-h or --help displays information on using the script.Also see sgRestoreAuthBackup.

sgBackupLogSrv

[pwd=<password>][path=<destpath>][nodiskcheck][comment=<comment>][nofsstorage][-h | --help]

Creates a backup of Log Server configuration data. The backup file is stored in the <installation directory>/backups/ directory. Twice the size of log database is required on the destination drive. Otherwise, the operation fails.pwd entering a password enables encryption.path defines the destination path.nodiskcheck ignores free disk check before creating the backup.comment allows you to enter a comment for the backup. The maximum length of a comment is 60 characters.nofsstorage creates a backup only of the log server configuration without the log data.-h or --help displays information on using the script.Also see sgRestoreLogBackup.

sgBackupMgtSrv

[pwd=<password>][path=<destpath>][nodiskcheck][comment=<comment>][-h | --help]

Creates a complete backup of the Management Server (including both the local configuration and the stored information in the configuration database). The backup file is stored in the <installation directory>/backups/ directory. Twice the size of the Management Server database is required on the destination drive. Otherwise, the operation fails.pwd entering a password enables encryption.path defines the destination path.nodiskcheck ignores free disk check before creating the backup.comment allows you to enter a comment for the backup. The maximum length of a comment is 60 characters.-h or --help displays information on using the script.Also see sgRestoreMgtBackup and sgRecoverMgtDatabase.

Table A.1 Management Center Command Line Tools (Continued)

Command Description


sgCertifyAuthSrv

Contacts the Management Server and creates a new certificate for the Authentication Server to allow secure communications with other system components. Renewing an existing certificate does not require changing the configuration of any other system components.

sgCertifyLogSrv[host=<Management Server Address[\Domain]>]

Contacts the Management Server and creates a new certificate for the Log Server to allow secure communications with other system components. Renewing an existing certificate does not require changing the configuration of any other system components.host specifies the address of the Management Server. If the parameter is not defined, the loopback address (localhost) is used.Domain specifies the administrative Domain the Log Server belongs to if the system is divided in administrative Domains. If the Domain is not specified, the Shared Domain is used.The Log Server needs to be shut down before running this command. Restart the server after running this command.

sgCertifyMgtSrv

Creates a new certificate for the Management Server to allow secure communications between the Stonesoft system components. Renewing an existing certificate does not require changes on any other system components.The Management Server needs to be shut down before running this command. Restart the server after running this command

sgCertifyWebPortalSrv

[host=<Management Server Address[\Domain]>]

Contacts the Management Server and creates a new certificate for the Web Portal Server to allow secure communications with other system components. Renewing an existing certificate does not require changing the configuration of any other system components.host specifies the address of the Management Server. If the parameter is not defined, the loopback address (localhost) is used.Domain specifies the administrative Domain the Web Portal Server belongs to if the system is divided in administrative Domains. If the Domain is not specified, the Shared Domain is used.The Web Portal Server needs to be shut down before running this command. Restart the server after running this command.

sgChangeMgtIPOnAuthSrv <IP address>

Changes the Management Server’s IP address in the Authentication Server’s local configuration to the IP address you give as a parameter. Use this command if you change the Management Server’s IP address. Restart the Authentication Server after running this command.


Command Description


sgChangeMgtIPOnLogSrv <IP address>

Changes the Management Server’s IP address in the Log Server’s local configuration to the IP address you give as a parameter. Use this command if you change the Management Server’s IP address.Restart the Log Server service after running this command.

sgChangeMgtIPOnMgtSrv <IP address>

Changes the Management Server’s IP address in the local configuration to the IP address you give as a parameter. Use this command if you change the Management Server’s IP address.Restart the Management Server service after running this command.

sgClient Starts a locally installed Stonesoft Management Client.

sgCreateAdminCreates an unrestricted (superuser) administrator account.The Management Server needs to be stopped before running this command.

sgExport [host=<Management Server Address[\Domain]>] [login=<login name>][pass=<password>]file=<file path and name>[type=<all|nw|ips|sv|rb|al> [name= <element name 1, element name 2, ...>][recursion][-system][-h | -help | -?]

Exports elements stored on the Management Server to an XML file.Enclose details in double quotes if they contain spaces.host specifies the address of the Management Server. If the parameter is not defined, the loopback address (localhost) is used.Domain specifies the administrative Domain for this operation if the system is divided in administrative Domains. If the Domain is not specified, the Shared Domain is used.login defines the username for the account that is used for this operation. If this parameter is not defined, the username root is used.pass defines the password for the user account.file defines the name and location of the export ZIP file.type specifies which types of elements are included in the export file: all for all exportable elementsnw for network elementsips for IPS elementssv for servicesrb for security policiesal for alertsvpn for VPN elements.name allows you to specify by name the element(s) that you want to export.recursion includes referenced elements in the export, for example, the network elements used in a policy that you export.-system includes any system elements that are referenced by the other elements in the export.-h, -help, or -? displays information on using the script.


Command Description


sgHA [host=<Management Server Address[\Domain]>][login=<login name>][pass=<password>][master=<management server>][-set-active][-set-standby][-sync][-fullsync][-check][-retry][-isolate][-force][-h|-help|-?]

Controls highly available (active and standby) Management Servers.host specifies the address of the Management Server. If the parameter is not defined, the loopback address (localhost) is used.Domain specifies the administrative Domain for this operation if the system is divided in administrative Domains. If the Domain is not specified, the Shared Domain is used.login defines the username for the account that is used for this operation. If this parameter is not defined, the username root is used.pass defines the password for the user account.master defines the Management Server used as a master server for the operation.-set-active activates and locks all domains. -set-standby deactivates and unlocks all domains.-sync performs full database replication. This functions differently on a standby Management Server and an active Management Server. If you run it on an active Management Server, it replicates the active database to every standby Management Server that has the Include in Database Replication option selected in its properties. If you run it on a standby Management Server, it replicates the active database from the active Management Server only to this standby Management Server (regardless of whether the Include in Database Replication option is selected in the standby Management Server’s properties).-fullsync performs full database replication with active server backup.-check checks that the database is in sync with the active server.-retry retries replication if this has been stopped due to a recoverable error.m-isolate isolates the management server from database replication. This is an initial requirement for synchronization.-force enforces the operation even if all Management Servers are not in sync. Note that using this option may cause instability if used carelessly.-h, -help, or -? displays information on using the script.


Command Description


sgImport [host=<Management Server Address[\Domain]>][login=<login name>][pass=<password>]file=<file path and name>[-replace_all][-h|-help|-?]

Imports Stonesoft Management Server database elements from a Stonesoft XML file. When importing, existing (non-default) elements are overwritten if both the name and type match.host specifies the address of the Management Server. If the parameter is not defined, the loopback address (localhost) is used.Domain specifies the administrative Domain for this operation if the system is divided in administrative Domains. If the Domain is not specified, the Shared Domain is used.login defines the username for the account that is used for this operation. If this parameter is not defined, the username root is used.pass defines the password for the user account.file defines the ZIP file whose contents you want to import.-replace_all ignores all conflicts by replacing all existing elements with new ones. -h, -help, or -? displays information on using the script.

sgImportExportUser

[host=<Management Server Address[\Domain]>][login=<login name>][pass=<password>]action=<import|export>file=<file path and name>[-h|-help|-?]

Imports and exports a list of Users and User Groups in an LDIF file from/to a Stonesoft Management Server’s internal LDAP database. To import User Groups, all User Groups in the LDIF file must be directly under the stonesoft top-level group (dc=stonesoft).The user information in the export file is stored as plaintext. Handle the file securely.host specifies the address of the Management Server. If the parameter is not defined, the loopback address (localhost) is used.Domain specifies the administrative Domain for this operation if the system is divided in administrative Domains. If the Domain is not specified, the Shared Domain is used.login defines the username for the account that is used for this operation. If this parameter is not defined, the username root is used.pass defines the password for the user account.action defines whether users are imported or exported.file defines the file that is used for the operation.Example: sgImportExportUser login=admin pass=abc123 action=export file=c:\temp\exportedusers.ldif

-h, -help, or -? displays information on using the script.


Command Description


sgInfo

SG_ROOT_DIRFILENAME[fast][-nolog][-client][-h|-help|-?]

Creates a ZIP file that contains copies of configuration files and the system trace files. The resulting ZIP file is stored in the logged in user’s home directory. The file location is displayed on the last line of screen output. Provide the generated file to Stonesoft support for troubleshooting purposes.SG_ROOT_DIR Stonesoft Management Center installation directory.FILENAME name of output file.-nolog extended log server information is NOT collected.-client collects traces only from the Management Client.-h, -help, or -? displays information on using the script.

sgOnlineReplication

[login=<login name>][pass=<password>][active-server=<name of active server>][standby-server=<name of standby server>][standby-server-address=<IP address of standby server>][-nodisplay][-h|-help|-?]

Replicates the Management Server’s database from the active Management Server to the standby Management Server.Note! Use this script only if the secondary Management Server’s configuration has been corrupted, the secondary Management Server’s certificate has expired, or in new SMC installations if the automatic database replication between the Management Servers has not succeeded. Otherwise, synchronize the database through the Management Client (see Synchronizing Management Databases Manually (page 332) or use the sgHA command.pass defines the password for the user account.active-server option specifies the IP address of the active Management Server from which the Management database is replicated. standby-server option specifies the name of the standby Management Server to which the Management database is replicated.standby-server-address option specifies the IP address of the standby Management Server to which the Management database is replicated.-nodisplay sets a text only console.-h, -help, or -? displays information on using the script.The return values are:0 OK8 sgOnlineReplication.sh failed to initialize properly9 login failed11 unknown error12 bad command line arguments13 replication canceled by user.

sgReinitializeLogServer

Note! This script is located in <installation directory>/bin/install.Creates a new Log Server configuration if the configuration file has been lost.


Command Description


sgRestoreArchive <ARCHIVE_DIR>

Restores logs from archive files to the Log Server. This command is available only on the Log Server. ARCHIVE_DIR is the number of the archive directory (0 – 31) from where the logs will be restored. By default, only archive directory 0 is defined. The archive directories can be defined in the <installation directory>/data/LogServerConfiguration.txt file: ARCHIVE_DIR_xx=PATH.

sgRestoreAuthBackup

[-pwd=<password>][-backup=<backup file name>][-nodiskcheck][-h|-help]

Restores the Authentication Server user information from a backup file in the <installation directory>/backups/ directory.Apply the Authentication Server’s configuration after this command.-pwd defines a password for encrypted backup.-backup defines a name for the backup file.-nodiskcheck ignores free disk check before backup restoration.-h or -help displays information on using the script.

sgRestoreLogBackup

[-pwd=<password>][-backup=<backup file name>][-nodiskcheck][-overwrite-syslog-template][-h|-help]

Restores the Log Server (logs and/or configuration files) from a backup file in the <installation directory>/backups/ directory.Apply the Authentication Server’s configuration after this command.-pwd defines a password for encrypted backup.-backup defines a name for the backup file.-nodiskcheck ignores free disk check before backup restoration.-overwrite-syslog-template overwrites a syslog template file if found in the backup.-h or -help displays information on using the script.

sgRestoreMgtBackup

[-pwd=<password>][-backup=<backup file name>][-nodiskcheck][-h|-help]

Restores the Management Server (database and/or configuration files) from a backup file in the <installation directory>/backups/ directory.-pwd defines a password for encrypted backup.-backup defines a name for the backup file.-nodiskcheck ignores free disk check before backup restoration.-h or -help displays information on using the script.

sgRevert

Note! This script is located in <installation directory>/bin/uninstall.Reverts to the previous installation saved during the upgrade process. The previous installation can be restored at any time, even after a successful upgrade.


Command Description


sgShowFingerPrintDisplays the CA certificate’s fingerprint on the Management Server.

sgStartAuthSrv Starts the Authentication Server.

sgStartLogSrv Starts the Log Server and its database.

sgStartMgtDatabaseStarts the Management Server’s database. There is usually no need to use this script.

sgStartMgtSrv Starts the Management Server and its database.

sgStartWebPortalSrv Starts the Web Portal Server.

sgStopLogSrv Stops the Log Server.

sgStopMgtSrv Stops the Management Server and its database.

sgStopMgtDatabaseStops the Management Server’s database. There is usually no need to use this script.

sgStopWebPortalSrv Stops the Web Portal Server.

sgStopRemoteMgtSrv

[host=<Management Server Host Name>] [login=<login name>][pass=<password>][-h|-help|-?]

Stops the Management Server service when run without arguments. To stop a remote Management Server service, provide the arguments to connect to the Management Server.host is the Management Server’s host name if not localhost.login is a Stonesoft administrator account for the login.pass is the password for the administrator account.-h, -help, or -? displays information on using the script.


Command Description


Engine Commands

The commands in the following two tables can be run on the command line on Firewall, Layer 2 Firewall, and/or IPS engines.

sgTextBrowser

[host=<Management Server address[\Domain]>][login=<login name>][pass=<password>][format=<CSV|XML>][o=<output file>][f=<filter file> ][e=<filter expression> ] [m=<current|stored>][limit=<maximum number of unique records to fetch>]

[-h|-help|-?]

Displays or exports current or stored logs. This command is available on the Log Server.Enclose the file and filter names in double quotes if they contain spaces.host defines the address of the Management Server used for checking the login information. If this parameter is not defined, Management Server is expected to be on the same host where the script is run. If Domains are in use, you can specify the Domain the Log Server belongs to. If domain is not specified, the Shared Domain is used.login defines the username for the account that is used for this export. If this parameter is not defined, the username root is used.pass defines the password for the user account used for this operation.format defines the file format for the output file. If this parameter is not defined, the XML format is used.o defines the destination output file where the logs will be exported. If this parameter is not defined, the output is displayed on screen.f defines the Stonesoft exported filter file that you want to use for filtering the log data.e defines the filter that you want to use for filtering the log data. Type the name as shown in the Management Client. m defines whether you want to view or export logs as they arrive on the Log Server (current) or logs stored in the active storage directory (stored). If this option is not defined, the current logs are used.limit defines the maximum number of unique records to be fetched. The default value is unlimited.-h, -help, or -? displays information on using the script.


Command Description


Table A.2 Stonesoft Engine Command Line Tools

Command Engine Role Description

sg-blacklist show [-v] [-f FILENAME] |add [

[-i FILENAME] | [src IP_ADDRESS/MASK] [src6 IPv6_ADDRESS/PREFIX][dst IP_ADDRESS/MASK][dst6 IPv6_ADDRESS/PREFIX][proto {tcp|udp|icmp|NUM}] [srcport PORT{-PORT}][dstport PORT{-PORT}][duration NUM]] |del [

[-i FILENAME] | [src IP_ADDRESS/MASK] [src6 IPv6_ADDRESS/PREFIX][dst IP_ADDRESS/MASK][dst6 IPv6_ADDRESS/PREFIX][proto {tcp|udp|icmp|NUM}] [srcport PORT{-PORT}][dstport PORT{-PORT}][duration NUM]] |iddel NODE_ID ID |flush

Firewall, Layer 2 Firewall, IPS

Can be used to view, add, or delete active blacklist entries. The blacklist is applied as defined in Access Rules.Commands:show displays the current active blacklist entries in format: engine node ID | blacklist entry ID | (internal) | entry creation time | (internal) | address and port match | originally set duration | (internal) | (internal). Use the -f option to specify a storage file to view (/data/blacklist/db_<number>). The -v option adds operation’s details to the output.add creates a new blacklist entry. Enter the parameters (see below) or use the -i option to import parameters from a file.del deletes the first matching blacklist entry. Enter the parameters (see below) or use the -i option to import parameters from a file.iddel NODE_ID ID removes one specific blacklist entry on one specific engine. NODE_ID is the engine’s ID, ID is the blacklist entry’s ID (as shown by the show command).flush deletes all blacklist entries.Add/Del Parameters:Enter at least one parameter. The default value is used for the parameters that you omit. You can also save parameters in a text file; each line in the file is read as one blacklist entry.src IP_ADDRESS/MASK defines the source IP address and netmask to match. Matches any IP address by default.src6 IPv6_ADDRESS/PREFIX defines the source IPv6 and prefix length to match. Matches any IPv6 address by default.dst IP_ADDRESS/MASK defines the destination IP address and netmask to match. Matches any IP address by default.dst6 IPv6_ADDRESS/PREFIX defines the destination IPv6 address and prefix length to match. Matches any IPv6 address by default.proto {tcp|udp|icmp|NUM} defines the protocol to match by name or protocol number. Matches all IP traffic by default.srcport PORT[-PORT] defines the TCP/UDP source port or range to match. Matches any port by default.dstport PORT[-PORT] defines the TCP/UDP destination port or range to match. Matches any port by default.duration NUM defines in seconds how long the entry is kept. Default is 0, which cuts current connections, but is not kept.Examples:sg-blacklist add src 192.168.0.2/32 proto tcp dstport 80 duration 60 sg-blacklist add -i myblacklist.txt sg-blacklist del dst 192.168.1.0/24 proto 47

81Engine Commands

sg-bootconfig

[--primary-console=tty0|ttyS PORT,SPEED][--secondary-console= [tty0|ttyS PORT,SPEED]][--flavor=up|smp][--initrd=yes|no][--crashdump=yes|no|Y@X][--append=kernel options][--help]apply


Can be used to edit boot command parameters for future bootups.--primary-console=tty0|ttyS PORT,SPEED parameter defines the terminal settings for the primary console.--secondary-console= [tty0|ttyS PORT,SPEED] parameter defines the terminal settings for the secondary console.--flavor=up|smp [-kdb] parameter defines whether the kernel is uniprocessor or multiprocessor.--initrd=yes|no parameter defines whether Ramdisk is enabled or disabled.--crashdump=yes|no|Y@X parameter defines whether kernel crashdump is enabled or disabled, and how much memory is allocated to the crash dump kernel (Y). The default is 24M. X must always be 16M.--append=kernel options parameter defines any other boot options to add to the configuration.--help parameter displays usage information.apply command applies the specified configuration options.

sg-clear-all


Note! Use this only if you want to clear all configuration information from the engine.This command resets all configuration information from the engine. It does not remove the engine software. After using this command, you must reconfigure the engine using the sg-reconfigure command.

sg-cluster

[status [-c SECONDS]][online][lock-online][offline][lock-offline][standby][safe-offline]

Firewall

Used to display or change the status of the node.status [-c SECONDS] command displays cluster status. When -c SECONDS is used, status is shown continuously with the specified number of seconds between updates.online command sends the node online.lock-online command sends the node online and keeps it online even if another process tries to change its state.offline command sends the node offline.lock-offline command sends the node offline and keeps it offline even if another process tries to change its state.standby command sets an active node to standby.safe-offline command sets the node to offline only if there is another online node.

sg-contact-mgmt


Used for establishing a trust relationship with the Management Server as part of engine installation or reconfiguration (see sg-reconfigure below). The engine contacts the Management Server using the one-time password created when the engine’s initial configuration is saved.

Table A.2 Stonesoft Engine Command Line Tools (Continued)



sg-dynamic-routing [start][stop][restart][force-reload][backup <file>][restore <file>][sample-config][route-table][info]

Firewall

start starts the Quagga routing suite.stop stops the Quagga routing suite and flushes all routes made by zebra.restart restarts the Quagga routing suite.force-reload forces reload of the saved configuration.backup <file> backs up the current configuration to a compressed file.restore <file> restores the configuration from the specified file.sample-config creates a basic configuration for Quagga.route-table prints the current routing table.info displays the help information for the sg-dynamic-routing command, and detailed information about Quagga suite configuration with vtysh.

sg-ipsec -d

[-u <username[@domain]> |-si <session id> |-ck <ike cookie> |-tri <transform id>-ri <remote ip> |-ci <connection id>]

Firewall

Deletes VPN-related information (use vpninfo command to view the information). Option -d (for delete) is mandatory.-u deletes the VPN session of the named VPN client user. You can enter the user account in the form <username@domain> if there are several user storage locations (LDAP domains).-si deletes the VPN session of a VPN client user based on session identifier.-ck deletes the IKE SA (Phase one security association) based on IKE cookie.-tri deletes the IPSEC SAs (Phase two security associations) for both communication directions based on transform identifier.-ri deletes all SAs related to a remote IP address in gateway-to-gateway VPNs.-ci deletes all SAs related to a connection identifier in gateway-to-gateway VPNs.

sg-logger

-f FACILITY_NUMBER -t TYPE_NUMBER

[-e EVENT_NUMBER] [-i "INFO_STRING"][-s] [-h]


Can be used in scripts to create log messages with the specified properties.-f FACILITY_NUMBER parameter defines the facility for the log message.-t TYPE_NUMBER parameter defines the type for the log message.-e EVENT_NUMBER parameter defines the log event for the log message. The default is 0 (H2A_LOG_EVENT_UNDEFINED).-i "INFO_STRING" parameter defines the information string for the log message.-s parameter dumps information on option numbers to stdout-h parameter displays usage information.



83Engine Commands

sg-raid

[-status] [-add] [-re-add] [-force] [-help]


Configures a new hard drive. This command is only for Stonesoft appliances that support RAID (Redundant Array of Independent Disks) and have two hard drives.-status option displays the status of the hard drive.-add options adds a new empty hard drive. Use -add -force if you want to add a hard drive that already contains data and you want to overwrite it.-re-add adds a hard drive that is already partitioned. This command prompts for the drive and partition for each degraded array. Use -re-add -force if you want to check all the arrays.-help option option displays usage information.

sg-reconfigure

[--boot][--maybe-contact][--no-shutdown]


Used for reconfiguring the node manually.--boot option applies bootup behavior. Do not use this option unless you have a specific need to do so.--maybe-contact option contacts the Management Server if requested. This option is only available on firewall engines.--no-shutdown option allows you to make limited configuration changes on the node without shutting it down. Some changes may not be applied until the node is rebooted.

sg-selftest [-d] [-h] FirewallRuns cryptography tests on the engine.-d option runs the tests in debug mode.-h option displays usage information.

sg-status [-l] [-h]


Displays information on the engine’s status.-l option displays all available information on engine status.-h option displays usage information.




sg-toggle-activeSHA1 SIZE |--force [--debug]


Switches the engine between the active and the inactive partition. This change takes effect when you reboot the engine.You can use this command, for example, if you have upgraded an engine and want to switch back to the earlier engine version. When you upgrade the engine, the active partition is switched. The earlier configuration remains on the inactive partition. To see the currently active (and inactive) partition, see the directory listing of /var/run/stonegate (ls -l /var/run/stonegate).The SHA1 SIZE option is used to verify the signature of the inactive partition before changing it to active. If you downgrade the engine, check the checksum and the size of the earlier upgrade package by extracting the signature and size files from the sg_engine_[version.build]_i386.zip file.--debug option reboots the engine with the debug kernel.--force option switches the active configuration without first verifying the signature of the inactive partition.

sg-upgrade FirewallUpgrades the node by rebooting from the installation CD-ROM. Alternatively, the node can be upgraded remotely using the Management Client.

sg-version


Displays the software version and build number for the node.

sginfo

[-f] [-d] [-s] [-p] [--] [--help]


Gathers system information you can send to Stonesoft support if you are having problems. Use this command only when instructed to do so by Stonesoft support.-f option forces sgInfo even if the configuration is encrypted.-d option includes core dumps in the sgInfo file.-s option includes slapcat output in the sgInfo file.-p option includes passwords in the sgInfo file (by default passwords are erased from the output).-- option creates the sgInfo file without displaying the progress--help option displays usage information.



85Engine Commands

The table below lists some general Linux operating system commands that may be useful in running your engines. Some commands can be stopped by pressing Ctrl+c.

Table A.3 General Command Line Tools on Engines

Command Description

dmesg Shows system logs and other information. Use the -h option to see usage.

halt Shuts down the system.

ipDisplays IP address information. Type the command without options to see usage. Example: type ip addr for basic information on all interfaces.

pingTests connectivity with ICMP echo requests. Type the command without options to see usage.

ps Reports the status of running processes.

reboot Reboots the system.

scp Secure copy. Type the command without options to see usage.

sftp Secure FTP. Type the command without options to see usage.

sshSSH client (for opening a terminal connection to other hosts). Type the command without options to see usage.

tcpdump

Gives information on network traffic. Use the -h option to see usage. You can also analyze network traffic by creating tcpdump files from the Stonesoft Management Client GUI with the Traffic Capture feature. See Taking a Traffic Capture (page 123).

topDisplays the top CPU processes taking most processor time. Use the -h option to see usage.

tracerouteTraces the route packets take to the specified destination. Type the command without options to see usage.

vpninfoDisplays VPN information and allows you to issue some basic commands. Type the command without options to see usage.


Server Pool Monitoring Agent Commands

You can test and monitor the Server Pool Monitoring Agents on the command line with the commands described in the table below.

Table A.4 Server Pool Monitoring Agent Commands

Command Description

agent[-v level]

[-c path]

[test [files]][syntax [files]]

(Windows only) Allows you to test different configurations before activating them.-v level Set the verbosity level. The default level is 5. Levels 6-8 are for debugging where available.-c path Use the specified path as the first search directory for the configuration.test [files]Run in the test mode - status queries do not receive a response. If you specify the files, they are used for reading the configuration instead of the default files. The output is directed to syslog or eventlog instead of the console where the command was run unless you use the -d option.syntax [files]

Check the syntax in the configuration file. If no files are specified, the default configuration files are checked.

sgagentd [-d] [-v level]

[-c path]

[test [files]][syntax [files]]

(Linux only) Allows you to test different configurations before activating them.-d Don’t Fork as a daemon. All log messages are printed to stdout or stderr only.-v level Set the verbosity level. The default level is 5. Levels 6-8 are for debugging where available.-c path Use the specified path as the first search directory for the configuration.test [files]Run in the test mode - status queries do not receive a response. If you specify the files, they are used for reading the configuration instead of the default files. The output is directed to syslog or eventlog instead of the console where the command was run unless you use the -d option.syntax [files]

Check the syntax in the configuration file. If no files are specified, the default configuration files are checked. The output is directed to syslog or eventlog instead of the console where the command was run unless you use the -d option.

87Server Pool Monitoring Agent Commands

sgmon [status|info|proto][-p port] [-t timeout]

[-a id]host

Sends a UDP query to the specified host and waits for a response until received, or until the timeout limit is reached.The request type can be defined as a parameter. If no parameter is given, status is requested. The commands are:status - query the status.info - query the agent version.proto - query the highest supported protocol version.-p port Connect to the specified port instead of the default port.-t timeout Set the timeout (in seconds) to wait for a response.-a id Acknowledge the received log messages up to the specified id. Each response message has an id, and you may acknowledge more than one message at a given time by using the id parameter. Note that messages acknowledged by sgmon will no longer appear in the firewall logs.host The IP address of the host to connect to. To get the status locally, you may give localhost as the host argument. This parameter is mandatory.Return value:0 if the response was received1 if the query timed out-1 in case of an error

Table A.4 Server Pool Monitoring Agent Commands (Continued)

Command Description


APPENDIX B

DEFAULT COMMUNICATION PORTS

This chapter lists the default ports used in connections between Stonesoft components and the default ports Stonesoft components use with external components.


Management Center Ports (page 90)Security Engine Ports (page 93)

89

Management Center Ports

The illustrations below present an overview to the most important default ports used in communications between the Stonesoft Management Center (SMC) components and from the SMC to external services. See the table below for a complete list of default ports.

Illustration B.1 Destination Ports for Basic Communications Within SMC

Illustration B.2 Default Destination Ports for Optional SMC Components and Features

TCP:8914-8918

Log Server Management Server

TCP:8902-8913

3021 (Log Server Certificate Request)

3023

Management Client

Management Server

Stonesoft’s Update Service

External LDAP Server

External RADIUS Server

TCP:443

TCP:389

UDP:1812

Additional Management Server

Log Server

Web Portal Server

TCP:8902-8913,

8916, 8917, 3023+ 3021

(Certificate Request)

TCP:302089168917

TCP:89038907

TCP:8902-8913

Monitored Third Party

Components

UDP:161

TCP, UDP:162/5162514/5514Win/Linux)

TCP: 8925 - 8929


TCP:8907+ 3021 (Certificate Request)

TCP:3020

90 Appendix B Default Communication Ports

The table below lists all default ports SMC uses internally and with external components. Many of these ports can be changed. The name of corresponding default Service elements are also included for your reference. For information on communications between SMC components and the engines, see the separate listings.

Table B.1 Management Center Default Ports

Listening Host

Port/Protocol

Contacting Hosts Service Description Service Element

Name

Additional Management Servers

8902- 8913/TCP

Management Server

Database replication (push) to the additional Management Server.

SG Control


8925-8929/TCP

Management Server

Stonesoft Management Server commands to Authentication Server.

SG Authentication Commands

Authentication Server node

8988-8989/TCP

Authentication Server node

Data synchronization between Authentication Server nodes.

SG Authentication Sync

DNS server53/UDP,53/TCP

Management Client, Management Server, Log Server

DNS queries. DNS (UDP)

LDAP server 389/TCPManagement Server

External LDAP queries for display/editing in the Management Client.

LDAP (TCP)

Log Server162/UDP,5162/UDP

Monitored third party components

SNMPv1 trap reception from third party components. Port 162 is used if installed on Windows, port 5162 if installed on Linux.

SNMP (UDP)

Log Server

514/TCP, 514/UDP, 5514/TCP, 5514/UDP

Monitored third party components

Syslog reception from third party components. Port 514 is used if installed on Windows, port 5514 if installed on Linux.

Syslog (UDP)[Partial match]

Log Server 3020/TCP

Authentication Server, Log Server,Web Portal Server,Security Engines

Alert sending from the Authentication Server, Log Server, and Web Portal Server.Log and alert messages; monitoring of blacklists, connections, status, and statistics from Security Engines.

SG Log

Log Server8914-8918/TCP

Management Client

Log browsing. SG Data Browsing

Log Server8916-8917/TCP

Web Portal Server Log browsing.SG Data Browsing (Web Portal Server)

Management Server

3021/TCPLog Server, Web Portal Server

System communications certificate request/renewal.

SG Log Initial Contact

91Management Center Ports

Management Server

8902-8913/TCP

Management Client, Log Server, Web Portal Server

Monitoring and control connections. SG Control

Management Server

3023/TCP

Management Server, Log Server, Web Portal Server

Log Server and Web Portal Server status monitoring.Status information sent from a Management Server in one Domain to a Management Server in another Domain.

SG Status Monitoring

Management Server

8903, 8907/TCP

Additional Management Servers

Database replication (pull) to the additional Management Server.

SG Control

Management Server

8907/TCPAuthentication Server

Status monitoring. SG Control

Monitored Third Party Components

161/UDP Log ServerSNMP status probing to external IP addresses.

SNMP (UDP)

RADIUS server 1812/UDPManagement Server

RADIUS authentication requests for administrator logins. The default ports can be modified in the properties of the RADIUS Server element.

RADIUS (Authentication)

Stonesoft servers

443/TCPManagement Server

Update packages, engine upgrades, and licenses from update.stonesoft.com and smc.stonesoft.com.

HTTPS

Syslog Server514/UDP, 5514/UDP

Log ServerLog data export to syslog servers. The default ports can be modified in the LogServerConfiguration.txt file.

Syslog (UDP)[Partial match]

Table B.1 Management Center Default Ports (Continued)

Listening Host

Port/Protocol

Contacting Hosts Service Description Service Element

Name


Security Engine Ports

The illustrations below present an overview to the most important default ports used in communications between Security Engines and the SMC and between clustered Security Engine nodes. See the table below for a complete list of default ports for the engines.

Illustration B.3 Destination Ports for Basic Security Engine Communications

Illustration B.4 Default Destination Ports for Security Engine Service Communications

Other Node(s) in the ClusterLog Server

Security Engine

Management Server

TCP:

3020TCP:636

495049878888

Or none*TCP:30213023

8906*

*Single engines with “Node-initiated Contact to Management Server” selected.

TCP:300230033010

UDP:30003001

Multicast(Heartbeat interfaces)

Server Pool*

DNS Server

LDAP Server* RADIUS Server* TACACS+ Server*

DHCP Server* SNMP Server

RPCServer*

Security Engine

VPN Clients*

VPNGateways*UDP:

50027464500

UDP:68

UDP:161UDP:

67UDP:162

TCP, UDP:111

UDP:7777

TCP:389636

UDP:18121645

TCP, UDP:53

TCP:49

UDP:500

4500 UDP:500

27464500

User Agent*

TCP:16661

* Engines in the Firewall/VPN role only.

93Security Engine Ports

The table below lists all default ports the Security Engines use internally and with external components. Many of these ports can be changed. The name of corresponding default Service elements are also included for your reference.

Table B.2 Security Engine Default Ports

Listening Host Port/Protocol Contacting

Hosts Service Description Service Element Name

Anti-virus signature server

80/TCP Firewall Anti-virus signature update service. HTTP


8925-8929/TCP

FirewallUser directory and authentication services.

LDAP (TCP), RADIUS (Authentication)

BrightCloud Server

2316/TCPFirewall, Layer 2 Firewall, IPS

BrightCloud web filtering update service.

BrightCloud update

DHCP server 67/UDP FirewallRelayed DHCP requests and requests from a firewall that uses dynamic IP address.

BOOTPS (UDP)

DNS server53/UDP, 53/TCP

Firewall Dynamic DNS updates. DNS (TCP)

Firewall 67/UDP Any DHCP relay on firewall engine. BOOTPS (UDP)

Firewall 68/UDP DHCP server Replies to DHCP requests. BOOTPC (UDP)

Firewall 500/UDPVPN clients, VPN gateways

VPN negotiations, VPN traffic. ISAKMP (UDP)

Firewall 636/TCPManagement Server

Internal user database replication. LDAPS (TCP)

Firewall 2543/TCP AnyUser authentication (Telnet) for Access rules.

SG User Authentication

Firewall 2746/UDPStonesoft VPN gateways

UDP encapsulated VPN traffic.SG UDP Encapsulation

Firewall 4500/UDPVPN client, VPN gateways

VPN traffic using NAT-traversal. NAT-T

Firewall Cluster Node

3000-3001/UDP3002-3003, 3010/TCP

Firewall Cluster Node

Heartbeat and state synchronization between clustered Firewalls.

SG State Sync (Multicast), SG State Sync (Unicast), SG Data Sync



Remote upgrade.SG Remote Upgrade



Management Server commands and policy upload.

SG Commands




Connection monitoring for old engine versions (5.1 and earlier).

SG Legacy Monitoring


15000/TCPManagement Server, Log Server

Blacklist entries. SG Blacklisting


161/UDP SNMP server SNMP monitoring. SNMP (UDP)

IPS Cluster Node

3000-3001/UDP3002-3003, 3010/TCP

IPS Cluster Node

Heartbeat and state synchronization between clustered IPS engines.


LDAP server 389/TCP FirewallExternal LDAP queries, including StartTLS connections.

LDAP (TCP)

Layer 2 Firewall Cluster Node

3000-3001/UDP3002-3003, 3010/TCP

Layer 2 Firewall Cluster Node

Heartbeat and state synchronization between clustered Layer 2 Firewalls.


Log Server 3020/TCPFirewall, Layer 2 Firewall, IPS

Log and alert messages; monitoring of blacklists, connections, status, and statistics.

SG Log

Management Server


System communications certificate request/renewal (initial contact).

SG Initial Contact

Management Server


Monitoring (status) connection.SG Status Monitoring

Management Server


Management connection for single engines with “Node-Initiated Contact to Management Server” selected.

SG Dynamic Control

RADIUS server1812, 1645/UDP

Firewall RADIUS authentication requests.RADIUS (Authentication), RADIUS (Old)

RPC server111/UDP, 111/TCP

Firewall RPC number resolve.SUNRPC (UDP), Sun RPC (TCP)

Server Pool Monitoring Agents

7777/UDP FirewallPolls to the servers’ Server Pool Monitoring Agents for availability and load information.

SG Server Pool Monitoring

Table B.2 Security Engine Default Ports (Continued)



95Security Engine Ports

SNMP server 162/UDPFirewall, Layer 2 Firewall, IPS

SNMP traps from the engine. SNMP Trap (UDP)

TACACS+ server 49/TCP Firewall TACACS+ authentication requests. TACACS (TCP)

User Agent 16661/TCP FirewallQueries for matching Users and User Groups with IP addresses.

SG Engine to User Agent

VPN gateways

500/UDP, 2746/UDP (Stonesoft gateways only), or 4500 UDP.

FirewallVPN traffic. Ports 2746 and 4500 may be used depending on encapsulation options.

ISAKMP (UDP)

Table B.2 Security Engine Default Ports (Continued)




INDEX

Aadditional management servers, installing, 37–40administration client, see management clientauthentication server, installing, 27

Bbinding licenses, 33

Ccertificate authority

checking fingerprint, 31checksums, 14command line installation

see non-graphical installationcommand line tools, 69commands

engine, 80log server, 70management server, 70

compatibility with different platforms, 13contact addresses, 47–53

exceptions, 52contact information, 10customer support, 10

Ddatabase user account, 23date and time settings, 13demo mode, 28documentation available, 9

Eexceptions to contact addresses, 52

Ffile integrity, 14fingerprint of certificate authority, 31fingerprint of certificates, 79

Ggenerating server certificates, 35GUI client, see management client

Hhardware requirements, 10hosts file, 13

Iinstallation files, 14

creating CD-ROMs, 14integrity of files, 14

Jjava web start, 43–46

Llicenses, 15

binding, 33checking, 32, 61installing, 31, 61retained, 34upgrading, 15, 59–61

linux for management center, 20locations, 47–53log server

contact addresses, 51–53installing, 25starting, 34

Mmanagement bound licenses, 33management center

components, 12installing, 19–42upgrading, 62

management clientconfiguration files, 66installing, 20, 43–46installing using web start, 44–46logging in, 30setting location, 53starting, 30web start, 46

management servercontact addresses, 51–53database user account, 23installing, 23–24starting, 29

MD5 checksum, 14monitoring server, see web portal server

NNAT (network address translation), 47–53

locations, 47–53non-graphical installation, 41–42

Ooverview to the installation, 13

97Index

Pplanning installation, 11–15platforms supported, 13

Rrequirements for hardware, 10retained licenses, 34

Sservers

additional management servers, 37–40authentication server, 27certifying, 35log server, 25management server, 23–24starting manually, 34web portal server, 26

sgadmin user account, 20SHA-1 checksum, 14starting

log server, 34management client, 30management server, 29servers manually, 34web portal server, 34

stonesoft architecture, 12support services, 10supported platforms, 13system architecture, 12system requirements, 10

Ttechnical support, 10typographical conventions, 8

Uuninstalling, 65–66upgrading, 57–64

licenses, 59–61management center, 62

Wweb portal server

installing, 26starting, 34

web start, 43–46enabling web start server, 44–45

web start filescreating manually, 45–46

98 Index

Stonesoft Guides

Administrator’s Guides - step-by-step instructions for configuring and managing the system.

Installation Guides - step-by-step instructions for installing and upgrading the system.

Reference Guides - system and feature descriptions with overviews to configuration tasks.

User's Guides - step-by-step instructions for end-users.

For more documentation, visit

www.stonesoft.com/support/

Stonesoft Corporation

Itälahdenkatu 22 AFI-00210 Helsinki

Finland

Tel. +358 9 476 711Fax +358 9 4767 1349

Stonesoft Inc.

1050 Crown Pointe ParkwaySuite 900Atlanta, GA 30338USA

Tel. +1 770 668 1125Fax +1 770 668 1131

Copyright 2012 Stonesoft Corporation. All rights reserved. All specifications are subject to change.

http://www.stonesoft.com/en/support/

Documents

Security Management Center (SMC) powered by …...8 Chapter 1 Using Stonesoft Documentation How to Use This Guide The Management Center Installation Guide is intended for the administrators