GTA Reporting Suite 2 Guide

GTA Reporting Suite
Version 2.0
User’s Guide
GTARSUG200802-01
ii GTA Reporting Suite 2.0 User’s Guide Contents
Contents
Introduction 1
About GTA Reporting Suite 2.0… ………………………………………………………………………………………………………… 1
Features… ………………………………………………………………………………………………………………………………… 1
Requirements……………………………………………………………………………………………………………………………… 1
About the GTA Firewall Control Center… ……………………………………………………………………………………………… 2
Firewall Control Center Server… ……………………………………………………………………………………………………… 2
GTA Reporting Suite 2.0 Database Backend… ……………………………………………………………………………………… 2
GTA Reporting Suite 2.0 Client… ……………………………………………………………………………………………………… 2
Registration…………………………………………………………………………………………………………………………………… 2
Installation Support… ……………………………………………………………………………………………………………………… 3
Support Options…………………………………………………………………………………………………………………………… 3
Documentation… …………………………………………………………………………………………………………………………… 3
Additional Documentation……………………………………………………………………………………………………………… 3
Installation 4
Configuring the Firewall… ………………………………………………………………………………………………………………… 5
About Firewall Pre-shared Secrets……………………………………………………………………………………………………… 5
Installing GTA Reporting Suite 2.0………………………………………………………………………………………………………… 6
Microsoft Windows… …………………………………………………………………………………………………………………… 6
Full Installation… ……………………………………………………………………………………………………………………… 7
Server Only Installation………………………………………………………………………………………………………………… 10
Database Backend Only Installation… ……………………………………………………………………………………………… 12
Documentation Only Installation……………………………………………………………………………………………………… 14
Linux… …………………………………………………………………………………………………………………………………… 15
Server Installation… …………………………………………………………………………………………………………………… 16
Database Backend Only Installation… ……………………………………………………………………………………………… 18
Reinstalling GTA Reporting Suite 2.0 (Windows)… …………………………………………………………………………………… 20
Using GTA Reporting Suite 2.0 21
Connecting to the Firewall Control Center Server… ………………………………………………………………………………… 21
Launching the GTA Reporting Suite 2.0 Client… ……………………………………………………………………………………… 22
Administrative Controls… ………………………………………………………………………………………………………………… 23
Firewalls… ………………………………………………………………………………………………………………………………… 23
Monitoring Firewalls… ………………………………………………………………………………………………………………… 23
Organizing Firewalls… ………………………………………………………………………………………………………………… 23
Removing Firewalls… ………………………………………………………………………………………………………………… 25
Editing Firewall Properties… ………………………………………………………………………………………………………… 25
User Administration… …………………………………………………………………………………………………………………… 26
Organizing Users… …………………………………………………………………………………………………………………… 26
Removing Users………………………………………………………………………………………………………………………… 29
Database Management… ……………………………………………………………………………………………………………… 30
Backing Up the Database……………………………………………………………………………………………………………… 30
Purging Records from the Database… ……………………………………………………………………………………………… 31
Restoring the Database… …………………………………………………………………………………………………………… 31
User Controls… ……………………………………………………………………………………………………………………………… 32
Launching the GTA Reporting Suite 2.0 Client………………………………………………………………………………………… 32
Running Reports… ……………………………………………………………………………………………………………………… 33
Query Parameters……………………………………………………………………………………………………………………… 34
Report Output…………………………………………………………………………………………………………………………… 34
Changing the Chart Display Format… ……………………………………………………………………………………………… 37
Printing Reports………………………………………………………………………………………………………………………… 37
Exporting Reports… …………………………………………………………………………………………………………………… 38
Importing Reports… …………………………………………………………………………………………………………………… 38
Reference A: User Interface 39
Menu Overview… …………………………………………………………………………………………………………………………… 39
File… ……………………………………………………………………………………………………………………………………… 39
View………………………………………………………………………………………………………………………………………… 39
Admin… …………………………………………………………………………………………………………………………………… 40
Reports… ………………………………………………………………………………………………………………………………… 40
Window… ………………………………………………………………………………………………………………………………… 40
Help………………………………………………………………………………………………………………………………………… 40
Action Buttons………………………………………………………………………………………………………………………………… 41
Movable Rulers… …………………………………………………………………………………………………………………………… 41
GTA Reporting Suite 2.0 User’s Guide Contents iii

Drag and Drop Tabs… ……………………………………………………………………………………………………………………… 42
Standard Icons… …………………………………………………………………………………………………………………………… 43
Reference B: Reports 45
Usage Summary……………………………………………………………………………………………………………………………… 45
“Top 10” Reports…………………………………………………………………………………………………………………………… 47
Security Policy Blocks… …………………………………………………………………………………………………………………… 49
“Top 10” Reports…………………………………………………………………………………………………………………………… 52
Alarms… ……………………………………………………………………………………………………………………………………… 54
“Top 10” Reports…………………………………………………………………………………………………………………………… 57
Internet Access Management……………………………………………………………………………………………………………… 58
“Top 10” Reports…………………………………………………………………………………………………………………………… 60
Surf Sentinel Reports… ………………………………………………………………………………………………………………… 61
“Top 10” Reports…………………………………………………………………………………………………………………………… 64
Mail Sentinel Reports… …………………………………………………………………………………………………………………… 67
Mail Sentinel Anti-Virus Reports………………………………………………………………………………………………………… 68
“Top 10” Reports…………………………………………………………………………………………………………………………… 68
Mail Sentinel Anti-Spam Reports… …………………………………………………………………………………………………… 69
Administrative Reports……………………………………………………………………………………………………………………… 70
FWCC Administrative Reports…………………………………………………………………………………………………………… 70
Firewall Administrative Reports… ……………………………………………………………………………………………………… 71
Reference C: Creating DSNs 73
Microsoft Windows… ……………………………………………………………………………………………………………………… 73
Creating DSNs Using MySQL…………………………………………………………………………………………………………… 73
Creating DSNs Using PostgreSQL……………………………………………………………………………………………………… 74
Creating DSNs Using MS SQL Server… ……………………………………………………………………………………………… 75
Creating the Firewall Control Center DSN…………………………………………………………………………………………… 75
Creating the Firewall Control Center Admin DSN…………………………………………………………………………………… 78
Linux… ………………………………………………………………………………………………………………………………………… 81
Creating an ODBC Driver………………………………………………………………………………………………………………… 81
Defining an ODBC Driver for MySQL………………………………………………………………………………………………… 81
Defining an ODBC Driver for PostgreSQL…………………………………………………………………………………………… 81
Installing the ODBC Driver… ………………………………………………………………………………………………………… 81
Creating DSNs Using MySQL…………………………………………………………………………………………………………… 82
Installing the DSN… …………………………………………………………………………………………………………………… 82
Creating DSNs Using PostgreSQL……………………………………………………………………………………………………… 83
Installing the DSN… …………………………………………………………………………………………………………………… 83
Reference D: Troubleshooting 85
Installation Issues… ………………………………………………………………………………………………………………………… 85
Client Issues… ……………………………………………………………………………………………………………………………… 85
Server Issues… ……………………………………………………………………………………………………………………………… 87
Database Backend Issues… ……………………………………………………………………………………………………………… 89
iv GTA Reporting Suite 2.0 User’s Guide Contents

Introduction
A b o u t G TA R e p o r t i n g S u i t e 2 . 0
GTA Reporting Suite 2.0 provides clear, concise, top-level reports that enable administrators to
manage usage. This easy-to-use tool can be used to generate intuitive reports from GTA firewall
data sent to a supported ODBC-compliant database.
GTA Reporting Suite 2.0 is a component of the GTA Firewall Control Center. All components
work together from the Firewall Control Center Server, the central hub of the GTA Firewall Control
Center.
Features
• New, intuitive interface
• Historical reports
• Supports ODBC-compliant databases, including Microsoft SQL Server
• Usage Summary, Security Policy Blocks, Internet Access Reports and more
Requirements
Operating requirements:
• A GTA firewall running GB-OS 3.7 or greater
• Java Runtime Environment 1.6 or greater
Server requirements:
• A supported operating system:
• Microsoft Windows 2000 SP4, XP Professional SP2, Server 2003 SP1, or Vista Business
• Linux (Red Hat Enterprise Linux 5)
• 2 GHz Pentium 4 (minimum)
• 1 GB RAM (minimum)
• 20 MB hard drive space
• Storage space for the database
• Two (2) DSNs; One (1) for Firewall Control Center and one (1) for Firewall Control Center Admin
• Internet access
Database requirements (one of the following):
• Microsoft SQL Express
• Microsoft SQL Server
• MySQL 3.51.x, 4.0, 4.1 or 5.0 and ODBC driver
• PostgreSQL 8.0 or 8.1 and ODBC driver
GTA Reporting Suite 2.0 User’s Guide Introduction 1

A b o u t t h e G TA F i r e w a l l C o n t r o l C e n t e r
The GTA Firewall Control Center is a service that acts as the central hub for GTA’s network moni-
toring products, GB Commander 2.0 and GTA Reporting Suite 2.0. It offers one point access to all
GTA firewalls on your distributed network.
Firewall Control Center Server

The Firewall Control Center Server, a required component of GTA Reporting Suite 2.0, is a server
on your network that accepts GTA firewall data and redirects it to GTA Reporting Suite 2.0 Clients
for interpretation.
While GTA Reporting Suite 2.0 utilizes the Firewall Control Center Server, it is not necessary to
purchase a separate license for use of the Firewall Control Center Server.
G TA R e p o r t i n g S u i t e 2 . 0 D a t a b a s e B a c k e n d
The GTA Reporting Suite 2.0 Database Backend is the repository for all data sent from GTA fire-
walls that are configured to send logging information to the Firewall Control Center Server. The
Database Backend can either be installed on the same server as the Firewall Control Center Server,
or separately.
Administrators may back up, purge and restore the database using the GTA Reporting Suite 2.0
Client.
G TA R e p o r t i n g S u i t e 2 . 0 C l i e n t
The GTA Reporting Suite 2.0 Client is a platform-independent Java-based client that is used to run
reports using data from the Database Backend. The GTA Reporting Suite 2.0 Client is launched
from the Firewall Control Center Server.
Registration
Be sure to register your GTA Reporting Suite 2.0 product at GTA’s Online Support Center (https://
www.gta.com/support/center/login/). Registering your product provides access to product
updates and support.
To register your copy of GTA Reporting Suite 2.0 login to the GTA Online Support Center and go to
Register Product. In the Serial Number field enter your GTA Reporting Suite 2.0 serial number. In the
Verification Code field enter your software installation code.
Note
The verification code is provided along with your GTA Reporting Suite 2.0 serial number.
2 GTA Reporting Suite 2.0 User’s Guide Introduction

Installation Support
Installation (“up and running”) support is available to registered users. See GTA’s website for more
information. If you need installation assistance, be sure to register your product and then contact
the GTA Technical Support team by email at support@gta.com. Please include your serial number
and a brief description of the problem in the body of the email.
Installation support covers only the aspects of configuration related to installation and default
setup of GTA Reporting Suite 2.0 and does not include installation or set-up of ODBC databases.
For further assistance, contact GTA Sales staff by email at sales@gta.com for more information
about support offerings.
Support Options
If you need support for GTA Products, a variety of support contracts are available. Contact GTA
Sales staff by email at sales@gta.com for more information. Contracts range from support by the
incident to full coverage for a year. Other assistance may be available through the GTA Users
Mailing List, GTA Firewall User Forum or an authorized GTA Channel Partner.
Documentation
A few conventions are used in this guide to help you recognize specific elements of the text. If you
are viewing this guide in PDF format, color variations may also be used to emphasize notes, warn-
ings and new sections.
Bold Italics Emphasis

Italics Publications
Blue Underline Clickable hyperlink (email address, web site or in-PDF link)
Small Caps On-screen field names
Monospace Font On-screen text
Condensed Bold On-screen menus, menu items
Bold Small Caps On-screen buttons, links
Additional Documentation
For instructions on installation, registration and setup of a GTA Firewall, see the GB-OS User’s
Guide. For optional features, see the appropriate Feature Guide. Manuals and other documenta-
tion can be found on the GTA website at http://www.gta.com/support/documents/.
Documents on the website are either in plain text (*.txt) or Portable Document Format (*.pdf),
which requires Adobe Acrobat Reader 5.0 or greater. A free copy of the Adobe Acrobat Reader
can be obtained from Adobe at www.adobe.com.
GTA Reporting Suite 2.0 User’s Guide Introduction 3

Installation
Prior to installing GTA Reporting Suite 2.0 it may be useful to have the following information at
hand:
• The IP address of the server that will have Firewall Control Center Server installed.
• If you are installing onto Microsoft Windows, the server’s IP address can be obtained
by running the IPConfig utility from the command prompt (Start>Run>cmd, hit Enter,
type ipconfig and Enter again).
• If you are installing onto Linux , the server’s IP address can be obtained by opening
Terminal and entering the ifconfig command.
• The GTA Reporting Suite 2.0 serial number and verification code.
If you had an Installation CD shipped to you, the serial number and verification code would have
been included in the packaging. Otherwise, the serial number and verification code would have
been emailed to you by GTA.
• The service owner’s user ID and password.
The service owner is a Windows user account with permissions to run as a service. If a service
owner does not exist or lacks the necessary rights, the GTA Reporting Suite 2.0 installer will cre-
ate one or ensure the existing user has the proper rights.
• The IP address of the Database Backend, if different from the Firewall Control Center Server.
• If you are installing onto Microsoft Windows, the Database Backend’s IP address can
be obtained by running the IPConfig utility from the command prompt (Start>Run>cmd,
hit Enter, type ipconfig and Enter again).
• If you are installing onto Linux , the Database Backend’s IP address can be obtained
by opening Terminal and entering the ifconfig command.
• The database manager host name or IP address and database type of the required DSNs.
If you are unsure of the location of your database manager host or the database type that
should be used, contact your systems administrator.
The server that will have GTA Reporting Suite 2.0 installed must also be connected to the Internet
for activation.
4 GTA Reporting Suite 2.0 User’s Guide Installation

Configuring the Firewall
Note
In order to monitor GTA firewalls using GTA Reporting Suite 2.0, it is required to configure the Firewall
Control Center service in the GTA firewalls’ GB-OS Web interface.
All firewalls to be monitored by GTA Reporting Suite 2.0 need to be configured to send logging
information to the Firewall Control Center Server. To do so, log in to your firewall under an admin-
istrative account and navigate to Configure>Services>Firewall Control Center.
Enable the Firewall Control Center service by selecting the Enable checkbox. In the Server field,
enter the IP address of the server you will be installing Firewall Control Center Server on and
append the port number (:2033) to the end. Under the Advanced tab, ensure the Binding Interface
is set to <AUTOMATIC>.
Optionally, you may enter a pre-shared secret. In the event that the pre-shared secrets between
the GTA firewall and GTA Reporting Suite 2.0 do not match, data will not be accepted by the
Firewall Control Center Server.
Once all the necessary information has been filled out, click Save.
Figure 2.1: Configuring the Firewall
About Firewall Pre-shared Secrets
Note
When discussing firewalls in the context of the Firewall Control Center Server, it is important to distinguish
between physical GTA firewalls and the Firewall Control Center representations of those firewalls. For
purposes of this discussion, physical firewalls will be called “GTA firewalls” and the Firewall Control
Center representations will be called “firewall objects”.
When a GTA firewall is configured to communicate with the Firewall Control Center Server the
configuration can include an optional pre-shared secret. This requires a matching pre-shared
secret to be configured for the corresponding firewall object or for the group containing the firewall
object. Without a matching pre-shared secret the GTA firewall will be unable to connect to the
The Firewall Control Center Server allows pre-shared secrets to be configured for individual firewall
objects and for firewall object groups. If a firewall object configured without a pre-shared secret is
moved into a group configured with a pre-shared secret the corresponding GTA firewall must be
configured with the group pre-shared secret. If a firewall object is configured with a pre-shared
secret the corresponding GTA firewall must be configured with the same pre-shared secret.
GTA Reporting Suite 2.0 User’s Guide Installation 5

I n s t a l l i n g G TA R e p o r t i n g S u i t e 2 . 0
GTA Reporting Suite 2.0 can either be installed onto a server running a supported copy of
Microsoft Windows or Linux. When installing the software, follow the instructions appropriate to
your server’s operating system.
Microsoft Windows
The installer is located on the Installation CD and can also be found in the GTA Online Support
Center (https://www.gta.com/support/center/) under Downloads>Additional Software. The installer will
install the desired software and/or documentation as well as create the necessary DSNs.
Caution
If you are upgrading from version 1.0.x or 1.1.x of GB Commander or GTA Reporting Suite, you will
need to backup your current database using DBManager and then uninstall any previous versions of
GB Commander, GTA Reporting Suite, as well as GTAsyslog. It is also necessary to delete the old GB
Commander or GTA Reporting Suite database.
GTA Reporting Suite 2.0 does not allow the importing of old data. Database backups from previous
versions are good for archival purposes only.
Please review the license agreement before installing GTA Reporting Suite 2.0. If you accept the
terms of the agreement, click the I Accept checkbox followed by the Next button.
There are four installation types to choose from:
• Full: Installs the Firewall Control Center Server, Database Backend and documentation.
• Server Only: Installs only the software necessary to run the Firewall Control Center Server.
• Database Backend Only: Installs only the software necessary to run the Database Backend.
• Documentation Only: Installs only GTA Reporting Suite 2.0 documentation.
Note
If you are installing the Database Backend, ensure that TCP/IP has been enabled as it is required for
the Database Backend to operate. Consult your database manager’s documentation for instruction.
Select your desired installation type and click Next.
Figure 2.2 Selecting the Installation Type

F u l l I n s t alla tio n
If you selected Full for your desired installation type, you will be prompted to enter your
GTA Reporting Suite 2.0 serial number and verification code. Once complete, click Next.
Figure 2.3: Entering the Serial Number and Verification Code
You will then be prompted to select the installation path where you wish to install the Firewall
Control Center Server. The default path (C:\Program Files\GTA) is recommended. Once selected, click
Next.
Figure 2.4: Selecting the Installation Path
The installer will next prompt for the service owner, which is a Windows account with permis-
sions to log on as a service. The Firewall Control Center Server and Database Backend both run
as services using the supplied service owner. The installer pre-populates the User ID field with a
suggested user name of gtauser. If you do not wish to use gtauser, enter your desired user
name. Enter and confirm the User ID’s password. Once complete, click Next. The installer will give
the user all necessary permissions to log on as a service and will also create the user if it does not
already exist.
Figure 2.5: Entering the Service Owner

When creating the DSNs (Data Source Names), enter the database manager host and select the
database type that the DSNs will use. The following options are available for the Database Type:
• SQL Server
• MySQL
• PostgreSQL
• Manual DSN Creation
If you select the <Manual DSN Creation> option, please refer to Reference C: Creating DSNs.
Note
If you are unsure of the location of your database manager host or the database type that should be
used, contact your system’s administrator.
Note
If you are installing GTA Reporting Suite 2.0 from the Installation CD, you will be prompted to install
SQL Express. If you choose to install SQL Express, GTA Reporting Suite 2.0 will create and configure
the necessary DSNs transparently.
Figure 2.6: Creating the DSN
If you selected SQL Server as your database type, you will be prompted with a dialog box asking if
the database is a SQL Server Named Instance. Click Yes to enter the SQL Server’s Instance Name.
Figure 2.7: Entering the Instance Name

For the Database Administrator, enter the User ID and Password as entered during installation of
your database manager. Typically, the PostgreSQL User ID will be postgres, the SQL Server User
ID will be sa and the MySQL User ID will be the database administrator’s user name. The Pass-
word will be the password entered during configuration of your database manager. Once complete,
click Next.
Figure 2.8: Entering the Database Administrator
When entering the Server Information, enter the server’s DNS resolvable host name (preferred)
or IP address. For example, server.example.com or 192.168.71.50. Once complete, click
Next.
Figure 2.9 : Entering Server Information
The SMTP Email Server Information section can be disregarded, since it does not apply to
GTA Reporting Suite 2.0. Once complete, click Install to finish the installation.
Figure 2.10: Entering Email Server Information

S e rv e r O nly In stalla tio n
If you selected Server Only for your desired installation type, you will be prompted to enter your
GTA Reporting Suite 2.0 serial number and verification code. Once complete, click Next.
Figure 2.11: Entering the Serial Number and Verification Code
You will then be prompted to select the installation path for Firewall Control Center Server. The
default path (C:\Program Files\GTA) is recommended. Once selected, click Next.
The installer will next prompt for the service owner, which is a Windows account with permissions
to log on as a service. The Firewall Control Center Server runs as a service using the supplied
service owner. The installer pre-populates the User ID field with a suggested user name of
gtauser. If you do not wish to use gtauser, enter your desired user name. Enter and confirm
the User ID’s password. Once complete, click Next. The installer will give the user all necessary
permissions to log on as a service and will also create the user if it does not already exist.

The next screen will prompt you to enter the Database Backend server host information. Enter the
DNS resolvable name (preferred) or IP address of the machine hosting the database server. For
example, server.example.com or 192.168.71.50. Once complete, click Next.
Figure 2.14: Entering the Database Server Host Information
When entering the Server Information, enter the server’s IP address or DNS resolvable host name.
For example, 192.168.71.50 or server.example.com. Once complete, click Next.
Figure 2.15: Entering Server Information
The SMTP Email Server Information section can be disregarded, since it does not apply to
GTA Reporting Suite 2.0. Once complete, click Install to finish the installation.
Figure 2.16: Entering Email Server Information

D a t a b a s e B ac k e n d On ly In st allat ion
If you selected Database Backend Only for your desired installation type, you will be prompted to select
the installation path for the Database Backend. The default path (C:\Program Files\GTA) is recom-
mended. Once selected, click Next.
The installer will next prompt for the service owner, which is a Windows account with permissions
to log on as a service. The Database Backend runs as a service using the supplied service owner.
The installer pre-populates the User ID field with a suggested user name of gtauser. If you do not
wish to use gtauser, enter your desired user name. Enter and confirm the User ID’s password.
Once complete, click Next. The installer will give the user all necessary permissions to log on as a
service and will also create the user if it does not already exist.

When creating the DSNs (Data Source Names), enter the database manager host and select the
database type that the DSNs will use. The following options are available for the Database Type:
• SQL Server
• MySQL
• PostgreSQL
• Manual DSN Creation
If you select the <Manual DSN Creation> option, please refer to Reference C: Creating DSNs.
Note
If you are unsure of the location of your database manager host or the database type that should be
used, contact your systems administrator.
Figure 2.19: Creating the DSN
If you selected SQL Server as your database type, you will be prompted with a dialog box asking if
the database is a SQL Server Named Instance. Click Yes to enter the SQL Server’s Instance Name.
Figure 2.20: Entering the Instance Name

For the Database Administrator, enter the User ID and Password as entered during installation of
your database manager. Typically, the PostgreSQL User ID will be postgres, the SQL Server User
ID will be sa and the MySQL User ID will be the database administrator’s user name. The Pass-
word will be the password entered during configuration of your database manager. Once complete,
click Next to complete the installation.
Figure 2.21: Entering the Database Administrator
D o c u me ntatio n On ly In stallat ion

If you selected Documentation Only for your desired installation type, documentation will be installed in
the default directory (C:\Program Files\GTA). Once selected, click Next to complete the installation.

Linux
Insert and mount the Installation CD if you plan to install from the CD. Installation files are also
available from the GTA Online Support Center (https://www.gta.com/support/center/) under
Downloads>Additional Software.
There are two installation files available:
• Server Installation: Installs the software necessary to run the Firewall Control Center Server.
• Database Backend Installation: Installs the software necessary to run the Database Backend.
Note
When you are installing the Database Backend, ensure that TCP/IP has been enabled as it is required
for the Database Backend to operate. Consult your database software package’s documentation for
instruction.
If the Linux server is to operate as the Database Backend, then a supported database software
package, ODBC driver and DSNs must be installed before the GTA Reporting Suite 2.0 Database
Backend installer can be run.
Note
For instructions on installing and configuring the supported database software package, refer to the
database software package’s documentation.
Note
For DSN configuration examples, refer to Reference C: Creating DSNs.

S e rv e r I ns talla tio n
If installing from the Installation CD, insert and mount the CD. Once mounted, navigate to the
Installers/FWCC/Linux directory. Located within the Linux directory are two installers:
GTA-FWCCdb-203.i386-RedHat.rpm.bin
GTA-FWCCserver-203.i386-RedHat.rpm.bin.
GTA-FWCCdb-203.i386-RedHat.rpm.bin is used to install the Database Backend while GTA-
FWCCserver-203.i386-RedHat.rpm.bin is used to install the Firewall Control Center Server.
Only the GTA-FWCCserver-203.i386-RedHat.rpm.bin installer is required when installing
the Firewall Control Center Server.
Running the Installer

To perform the installation, run the GTA-FWCCserver-203.i386-RedHat.rpm.bin installer in
Terminal. When the installer first launches, you will be prompted with a license agreement.
Figure 2.21: Accepting the License Agreement
Press the Enter or Spacebar keys to scroll through the on-screen text. If you agree to the terms of
the license agreement, type yes. The installer will then copy all necessary files.

Editing the Configuration File
After the installer has been run, it is necessary to edit the configuration file. The
GBCserver.conf file, located in /usr/local/etc/, contains configuration settings necessary for the
Firewall Control Center Server to operate. To edit the configuration file, open it in a text editor such
as gedit or kedit.
Figure 2.25: Configuring GBCserver.conf

Serial Number
Replace the value ChangeMe with the serial number. For example, Serial Number=”ChangeMe”
becomes Serial Number=”1234567890”.
Verification Code
Replace the value ChangeMe with the verification code. For example,
Verification Code=”ChangeMe” becomes Verification Code=”1234567890”.
Port
The Port Number is the port number that the server listens on. Default is “2033”. Enter another
value for the port number if you wish to use another port.
Host Name
When entering the host name, enter either the server’s IP address or DNS resolvable host name.
For example, “192.168.71.50” or “server.example.com”.
WWW File Path
The WWW file path is the location on the server where files for web client are stored. Default is “/
usr/local/sbin/FWCC/Web-Client”.
Data File Path
The data file path is the location on the server where data files are stored. If the entered value for
the directory does not exist, one will be created. The entered value for the data file path must be
different from the data file path defined in GBCdb.conf. Default is “/usr/local/sbin/FWCC/
GBCserverData”.
Runtime Cache
The runtime cache file path is the location on the server where GB-OS runtimes are temporarily
stored when runtimes are being updated by the GTA Reporting Suite 2.0 Client.
DB Address
Enter the IP address or DNS resolvable hostname of the Database Backend server. Since the
Database Backend server was installed on the same server as the Firewall Control Center Server,
the value should remain at its default value of “127.0.0.1”.
DB Port
The DB port is the port number that the Database Backend listens on. Default is “2034”. Enter
another value for the port number if you wish to use another port.
Predefinined FW Only
The predefined firewalls field configures whether the Firewall Control Center Server should allow
only predefined firewalls. When enabled, the server will send a disconnect to all undefined firewalls
and remove them from the system. Valid values are “True” and “False”. Default is “False”.
Email Server
Enter the DNS-resolvable name or IP address of the SMTP server that will be used to send alarm
email messages. This field does not apply to GTA Reporting Suite 2.0.
Alarm Email Address:
Enter the email address that will populate the “From” field in alarm email messages. This field
does not apply to GTA Reporting Suite 2.0.
Alarm Email Date in UTC
Enter “True” to utilize UTC time. Enter “False” to utilize system local time. Default is UTC.

Starting The Service
After the installer has been run and the configuration file has been edited, it is necessary to start
the GBCserver service. To do so, open Terminal (Applications>Accessories>Terminal) and enter
/sbin/service GBCserver start to start the GBCserver service.
The server only installation of GTA Reporting Suite 2.0 is now complete.
D a t a b a s e B ac k e n d On ly In st allat ion
If installing from the Installation CD, insert and mount the CD. Once mounted, navigate to Installers/
FWCC/Linux directory. Located within the Linux directory are two installers:
GTA-FWCCdb-203.i386-RedHat.rpm.bin
GTA-FWCCserver-203.i386-RedHat.rpm.bin.
GTA-FWCCdb-203.i386-RedHat.rpm.bin is used to install the Database Backend while GTA-
FWCCserver-203.i386-RedHat.rpm.bin is used to install the Firewall Control Center Server.
Only the GTA-FWCCdb-203.i386-RedHat.rpm.bin installer is required when installing the
Database Backend.
Running the Installer

To perform the installation, run the GTA-FWCCdb-203.i386-RedHat.rpm.bin installer in
Terminal (Applications>Accessories>Terminal). When the installer first launches, you will be prompted with
a license agreement.
Figure 2.26: Accepting the License Agreement
Press the Enter or Spacebar keys to scroll through the on-screen text. If you agree to the terms of
the license agreement, type yes. The installer will then copy all necessary files.

Editing the Configuration File
After the installer has been run, it is necessary to edit the configuration file. The
GBCdb.conf file, located in /usr/local/etc/, contains configuration settings necessary for the Firewall
Control Center Server to operate. To edit the configuration file, open it in a text editor such as
gedit or kedit.
Figure 2.27: Configuring GBCdb.conf
User DSN
Enter the connection string to be used for database communication. Values entered must
match their respective fields defined in the odbc.ini file. Default is “DSN=FWCC; UID=fwcc;
PWD=fwccpwd;”.
Admin DSN
Enter the connection string to be used for database communication. Values entered must match
their respective fields defined in the odbc.ini file. Default is “DSN=FWCC Admin; UID=ChangeMe;
PWD=ChangeMe”.
Host Name
When entering the host name, enter either the server’s IP address or DNS resolvable host name.
For example, “192.168.71.50” or “server.example.com”.
Port
The Port is the port number that the Database Backend listens on. Default is “2034”. Enter
another value for the port number if you wish to use another port.
Database XML
The Database XML file path is the location on the server where the Database.xml file is stored.
Default is “/usr/local/sbin/FWCC”.
Backup Files
The Backup Files file path is the location on the server where backed up files are to be stored.
Data File Path
The data file path is the location on the server where data files are stored. If the entered value for
the directory does not exist, one will be created. The entered value for the data file path must be
different from the data file path defined in GBCserver.conf. Default is “/usr/local/sbin/FWCC/
GBCdbData”.
Starting The Service

After the installer has been run and the configuration file has been edited, it is necessary to start
the GBCdb service. To do so, open Terminal (Applications>Accessories>Terminal) and enter
/sbin/service GBCdb start to start the GBCdb service.
The database backend only installation of GTA Reporting Suite 2.0 is now complete.

R e i n s t a l l i n g G TA R e p o r t i n g S u i t e 2 . 0
(Windows)
When installed on Microsoft Windows, GTA Reporting Suite 2.0 allows for updates without
completely uninstalling the software. To reinstall GTA Reporting Suite 2.0, either run the installer
from the Installation CD or download it from the GTA Support Center (https://www.gta.com/
support/center/) under Downloads>Additional Software.
Select the Reinstall radio button and click next to begin the procedure.
Figure 2.21: Reinstalling GTA Reporting Suite 2.0
Note
If you are upgrading to a later version of GTA Reporting Suite from GTA Reporting Suite 2.0, the Reinstall
radio button will read “Upgrade”.
Please review the license agreement before installing GTA Reporting Suite 2.0. If you accept the
terms of the agreement, click the I Accept checkbox followed by the Next button.
There are four types of installation to choose from (click the appropriate link for more information):
1. Full: Installs both the Firewall Control Center Server and Database Backend.
2. Server Only: Only installs the software necessary to run the Firewall Control Center Server.
3. Database Backend Only: Only installs the software necessary to run the Database Backend.
4. Documentation Only: Only installs documentation.
Select your desired installation method and click Next. When you are reinstalling
GTA Reporting Suite 2.0, fields will be pre-populated with settings entered during the previous
installation.
Note
If you have uninstalled GTA Reporting Suite 2.0 prior to reinstallation, it is necessary to reset your serial
number for reinstallation. For more information, see ...I cannot activate the service... in
Reference D: Troubleshooting.

U s i n g G TA R e p o r t i n g S u i t e 2 . 0
To run reports on monitored firewalls, GTA Reporting Suite 2.0 makes use of a platform-indepen-
dent Java-based client.
Connecting to the Firewall Control Center

Server
To connect to the Firewall Control Center Server open your Internet browser and enter the
Firewall Control Center Server’s IP address. To do so, enter the protocol prefix of https://. If
it is the same system as the one from which the client is being run, you may use localhost or
127.0.0.1. Append the port number of 2033 to the end of the URL by adding :2033.
Example: https://localhost:2033
If you are attempting to connect to the server from a remote connection, you will need to use the
server’s DNS resolvable name (preferred) or IP address.
Example: https://fwcc.gta.com:2033
This will connect you to the Firewall Control Center Server page. The server page is broken down
into the following sections:
• Start Client: Provides links to start the GTA Reporting Suite 2.0 Client as well as downloads for
required software.
• Server Status: Displays licensing, server and database information.
• E-Mail Support: Emails GTA Technical Support.
• Help: Opens online help.
Figure 3.1: Firewall Control Center Server Page
GTA Reporting Suite 2.0 User’s Guide Using GTA Reporting Suite 2.0 21
L a u n c h i n g t h e G TA R e p o r t i n g S u i t e 2 . 0
Client
To launch the GTA Reporting Suite 2.0 Client, click the Start Client link located on the left side of
the page and then click the Start button under Client. Once the software has launched, you will
be prompted with a login screen. The User ID and Password fields are case-sensitive. Enter your
account information and click Login.
If this is your first time logging into the GTA Reporting Suite 2.0 Client, enter the following:
User ID: Administrator
Password: fwccpwd
Note
Upon first use, the GTA Reporting Suite 2.0 Client will install a shortcut on the desktop. Doing so
removes the need to start the GTA Reporting Suite 2.0 Client from the Firewall Control Center Server.
Caution
For security purposes, GTA recommends changing the default user ID and password for the administrator
account. For information on changing account preferences, see User Administration.
Figure 3.2: Logging into the GTA Reporting Suite 2.0 Client
22 GTA Reporting Suite 2.0 User’s Guide Using GTA Reporting Suite 2.0
Administrative Controls
The following section describes common controls found in the GTA Reporting Suite 2.0 Client
available to a user with administrative permissions.
Firewalls
The Firewalls section of the GTA Reporting Suite 2.0 Client allows the user with necessary permis-
sions to organize firewalls into groups as well as run reports on them.
M o n i t o ri n g F irewa lls
In order to be able to run reports on your GTA firewall, it is necessary to move it out of the Not Moni-
tored group. Doing so allows you to run reports on the system. Moving firewalls from one group to
another can be done by dragging and dropping firewalls into the desired group.
Note
If your firewall is not displayed in the Not Monitored group, it may need to be configured to point to the
Firewall Control Center Server. For more information, see Configuring the Firewall.
Figure 3.3: Firewall List
O rg a n i z i n g F irewa lls
Firewalls can be organized by sorting them into groups. To add a new group or user, click on their
respective icon.
Figure 3.4: Adding Groups and Firewalls
Adding Firewall Groups

To create a firewall group, click the Add Group icon or right-click on a group and select New Group
from the menu.
Doing so opens the Add Group window. Enter the group name, and the Firewall Control Center’s
pre-shared secret, if configured. The pre-shared secret must match the pre-shared secret created
when configuring the firewall.
Figure 3.5: Adding a Firewall Group
Removing Firewall Groups

To remove a group, select a group and click the Remove Group icon or right-click on a group and
select Remove from the menu.
Caution
Removing a group will also remove all firewalls located within the group,
Figure 3.6: Remove Group Icon
Adding Firewalls
To add a new firewall to be monitored, click the Add Firewall icon or right-click on a group and
select New Firewall from the menu.
Doing so opens the Add Firewall window. Enter the firewall’s serial number. Optionally, you may
also enter the firewall’s logical name and the pre-shared secret (if configured). The pre-shared
secret must match the pre-shared secret created when configuring the firewall.
Note
If the firewall is added to a group, the firewall’s pre-shared secret will override the pre-shared secret
configured for the group.
Refer to Firewall Pre-shared Secrets for more information.
Figure 3.7: Adding a Firewall
R e mo v i n g F irewa lls
To remove a firewall, select the firewall and click the Remove Firewall icon or right-click on the
firewall and select Remove from the menu.
Figure 3.8: Remove Firewall Icon
E d i t i n g Firewa ll Pro p e rties

To edit a firewall’s properties, right-click on a firewall and select Properties from the menu. Editable
fields include the firewall’s logical name, the enable checkbox and preshared secret.
Table 3.1: Editable Firewall Properties

Field Description
Logical Name Enter a logical name for the firewall, if desired. E.g., GTA Firewall.
Refresh Rate This field is not used by GTA Reporting Suite 2.0.
Enable De-select the checkbox to disable the firewall. GTA Reporting Suite 2.0
will not accept data from a disabled firewall. Disabled firewalls will display
a grey icon and have “Disabled” appended to their name.
Enabled by default.
Preshared Secret (Mine) If entered, the firewall’s pre-shared secret must match the pre-shared
secret of the group the firewall is organized under. If the pre-shared
secrets do not match, data will not be retrieved.
If a pre-shared secret is entered, it will override Parent’s pre-shared secret.
This is useful if a firewall is organized under a group with a pre-shared
secret other than the one configured on the firewall; entering the firewall’s
preshared secret in the Mine field will allow for data to be retrieved.
For more information on pre-shared secrets and how they work, see
Configuring the Firewall.
Figure 3.9: Editing Firewall Properties
User Administration
The User Administration section allows the administrator to add and remove users as well as
organize them into groups.
To add a new group or user, click on their respective icon.
Figure 3.10: Adding Groups and Users
O rg a n i z i n g Use rs
Groups are used to organize users in a manageable order and to restrict privileges and firewall
access. For instance, a user with administrative rights may be grouped under Admin, while a user
with read-only privileges may be grouped under User or their company department.
Note
The default administrator account cannot be placed in a group.
Adding User Groups

To create a new group, click the Add Group icon or right-click on a group and select New Group from
the menu. Doing so opens the Add Group window.
Figure 3.11: Adding a Group
Enter a name for identification, and select the firewall group that will act as the root directory for
users in the group. By selecting a firewall group other than <All> as the Firewall Root, users orga-
nized within that group will not be able to access firewalls located outside their root directory.
Select the Permissions tab to set the specific default permissions for that group.
Note
Users with administrative permissions can edit the default permissions of the group to which they
belong but cannot change the user group name or firewall root group.
Table 3.2: User Group Permissions
Field Description
Special
Edit Tree Hierarchy Allows users organized under the configured user group to move users and
firewalls from one group node to another. Only firewalls organized under
the group’s Firewall Root level will be visible.
View Unmonitored Groups Allows users organized under a configured user group with a Firewall Root
of <All> to view firewalls in the Not Monitored firewall group.
Groups/Firewalls
View Allows users organized under the configured user group to view groups/
firewalls within their root level. Enabled by default. Permissions to view
firewalls cannot be disabled.
Create Allows users organized under the configured user group to create groups/
firewalls within their root level.
Modify Allows users organized under the configured user group to modify proper-
ties of groups/firewalls within their root level.
Delete Allows users organized under the configured user group to delete groups/
firewalls within their root level.
Figure 3.12: Configuring User Group Permissions
Removing User Groups

To remove a user group, select a group and click the Remove Group icon or right-click on a group
and select Remove from the menu.
Caution
Removing a group will also remove all users located within the group,
Figure 3.13: Remove Group Icon
Adding users
Additional user accounts may be created to log in to the GTA Reporting Suite 2.0 Client.
To create a new user, click the Add uSEr icon. Doing so opens the Add User window. The user’s
uSer id is required. Additional personal information, such as the user’s password, is optional.
Caution
For security reasons, GTA recommends setting a password for user accounts.
Figure 3.14: Adding a User
To configure the user’s permissions, select the Permissions tab. To have the user’s permissions
default to the permissions set for the user’s group, select the uSe group defaultS checkbox. To
override the group’s default settings and set the user’s permissions manually, disregard the uSe
group defaultS checkbox and configure the user’s permissions as desired.
Users organized under a user group with proper permissions can only:
• Create, modify or delete additional users or firewalls within their own user group or firewall root
level.
• Create, modify or delete additional user or firewall groups (sub groups) within their own user
group or firewall root level.
Users organized under a user group cannot:
• Change the properties of the user group they are organized under.
Table 3.3: User Permissions
Field Description
Special
Use Group Defaults Defaults the user’s permissions to those of the group they are organized
under.
Edit Tree Hierarchy Allows the user to move users and firewalls from one group node to
another. Only firewalls organized under the group’s Firewall Root level and
users organized under the user’s user group will be visible.
View Unmonitored Groups Allows the user configured under a group with a Firewall Root of <All> to
view firewalls in the Not Monitored firewall group.
Administrator Grants the user administrative rights. Administrators can create, modify
and delete users, user groups, firewalls and firewall groups as well as edit
the tree hierarchy.
Groups/Firewalls
View Allows the user to view groups/firewalls within their root level. Enabled by
default. Permission to view firewalls cannot be disabled.
Create Allows the user to create groups/firewalls within their root level.
Modify Allows the user to modify properties of groups/firewalls within their root
level.
Delete Allows the user to delete groups/firewalls within their root level.
Figure 3.15: Configuring User Permissions
R e mo v i n g Use rs
To remove a user, select the user and click the Remove User icon or right-click on the firewall and
select Remove from the menu.
Figure 3.16: Remove User Icon
Database Management
The Database Management window (located under Admin>Database Management), allows for the
backup, purging or restoration of the database.
Note
Database management is only available to administrators organized under the top-level (root) user
group.
B a c k i n g Up th e Datab as e
By backing up the database, a copy is stored for future recovery or reference. The database
remains unchanged. A backup does not remove any information.
To backup the database, first select the Backup radio button. Then, select the time period of
records you wish to backup and enter a filename. A time stamp in the format of
yyyymmdd_hhmm will be appended to the filename. Finally, select the records you wish to include
in the backup by enabling their checkboxes.
Once complete, click OK to perform the operation or Cancel to abort.
Figure 3.17: Backing Up the Database
Note
If GTA Reporting Suite 2.0 has been installed to the default location on a server running Microsoft
Windows, backups will be stored under C:\Program Files\GTA\Backup. The backup directory is user defined
on Linux installations.
Note
There is an automatic backup and purge that occurs on a nightly basis at midnight. By default it is set
to keep thirty days of alarm and report data. Log data will only be kept for seven days. All automatically
backed up data will be purged from the database.
P u rg i n g Rec o rd s fro m th e Dat abase
Purging old records from the database removes data to free up space in the database.
To purge the database of old records, first select the Purge radio button. Then, select the time
period of records you wish to purge and enter a filename if you are simultaneously backing the
records up. Finally, select the records you wish to purge by enabling their checkboxes. Purged
records are backed up by default. If you do not wish to back up records that are to be purged,
disable the Backup checkbox next to the record type.
Once complete, click OK to perform the operation or Cancel to abort.
Figure 3.18: Purging Records from the Database
R e s t o ri n g th e Datab as e
Restoring the database allows the user to return a previously stored backup to the database.
Restore functions are used in case of a system failure or to run reports on data that has previously
been purged from the database. The utility restores information exactly as it was saved from the
backup file.
To restore from a previously stored backup, first select the Restore radio button. Next, select the
backup from which you would like to restore. Once complete, click OK to perform the operation
or Cancel to abort.
Figure 3.19: Restoring the Database
Note
Backups from GTA Reporting Suite 1.0.x or 1.1.x are not compatible with GTA Reporting Suite 2.0 and
will not be recognized.
User Controls
The following section describes common controls found in the GTA Reporting Suite 2.0 Client that
are available to all users.
L a u n c h i n g t h e G TA R e p o r t i n g S u i t e 2 . 0 C l i e n t
To launch the GTA Reporting Suite 2.0 Client, navigate to the GTA Firewall Control Center Server
(e.g. https://fwcc.gta.com:2033). Click the Start Client link located on the left side of the
page and then click the Start button under Client. Once the software has launched, you will be
prompted with a login screen. Enter your User ID and Password and click Login.
Note
If you do not know the location of the server or your user ID and password, contact your system
administrator.
Note
Upon first use, the GTA Reporting Suite 2.0 Client will install a shortcut on the desktop. Doing so
removes the need to start the GTA Reporting Suite 2.0 Client from the Firewall Control Center Server.
Figure 3.20: Logging into the GTA Reporting Suite 2.0 Client
Running Reports
To run a report on a firewall, double-click on the desired firewall in the Firewalls menu or highlight it
and click the Report icon to open the Reports Menu.
Figure 3.21: Report Icon
Reports are broken down into the following categories in the Reports Menu:
• Usage Summary creates reports based on data transferred between two endpoints or the total
number of connections made to a URL.
• Security Policy Blocks summarizes the number of packets blocked by a security policy.
• Alarms summarizes alarm reports.
• Internet Access Management displays Surf Sentinel information. Certain reports require a
Surf Sentinel subscription.
• Mail Sentinel Reports displays Mail Sentinel information. Certain reports require a Mail Senti-
nel Anti-Virus or Anti-Spam subscription.
• Administrative Reports summarizes GTA Reporting Suite 2.0 and GTA firewall administrative
reports.
Note
For more information on reports and their requirements, please refer to Reference B: Reports.
Figure 3.22: Reports Menu
Q u e ry P a ra me ters
After selecting a report to run, the Send a Report Request dialog box will appear. Query param-
eters within the dialog box will vary by the type of report run. Select the desired data range by
completing fields required to run the report.
For example, to run a report on a specific IP address or user name that shows data collected
between two times and dates, enter that IP address in the Source IP Address or User Name field
along with the start and end times and dates in Start Time and End Time.
Figure 3.23: Sending a Report Request
Entering an IP Address or User Name

If prompted for an IP address or user name, leave the field blank to select all IP addresses or
user names. A wildcard can also be used to select a range of IP addresses (e.g., 192.168.1.*,
192.168.*, 192.*) or a range of user names (e.g., Joe*).
Date/Time Range
Use the Start Time and End Time selection to select the time period for which you wish to run the
report.
S h o w F i r e w a l l s To g g l e
Enable the Show Firewalls toggle to display an extra column in text-based reports that shows the
firewall from which log data originated.
R e p o rt O u tp u t
Reports are displayed in one of the following formats:
Tabular Text
Used for text-based reports. Data can be sorted in ascending or descending order by clicking on
a column title.
Figure 3.24: Tabular Text
Horizontal Bar Chart
Graphical chart representing values as horizontal bars whose lengths are proportional to the
values.
Figure 3.25: Horizontal Bar Chart
Vertical Bar Chart

Graphical chart representing values as vertical bars whose heights are proportional to the values.
Figure 3.26: Vertical Bar Chart
Line Graph
Graphical plot of one or more series of two-dimensional data. Data points for each series are
connected by lines. Each data series is color coded and has uniquely shaped plot points to differ-
entiate the data should the graph be printed in black and white.
Figure 3.27: Line Graph
Pie Chart
Graphical chart used when displaying data broken down into percentages.
Figure 3.28: Pie Chart
C h a n g i n g th e Ch a rt Dis p lay Format
To change the way a report is displayed, select either the contextual menu item Reports>Change Report
Format, the Change Report icon or right-click on the report and select Change Report Format from the
menu. Doing so will open the Select Display Format window.
Figure 3.29: Change Report Icon
To display the current report using other parameters, select an option from the Display Type pull-
down. While chart based reports can be displayed as tabular text, tabular text reports cannot be
displayed as a chart.
It is also possible to edit the title and subtitle of the report using their respective fields. Currently,
the Subtitle field is not supported in GTA Reporting Suite 2.0. Other parameters, such as 3-D
Display, Transparent, Show Labels and Show Legend can be shown or hidden by enabling or
disabling their checkbox.
Figure 3.30: Selecting the Display Format
P ri n t i n g Rep o rts
To print a report, select the desired report and either click the Print icon or select Print Report from
the Reports menu.
Figure 3.31: Print Icon
Only the currently selected window will print. You can also print reports by selecting the Print
option from the right-click menu.
Figure 3.32: Printing Reports
E x p o rt i n g Re p o rts
To save a report, select the desired report and either click the Export icon or select Export Report
from the Reports menu.
Figure 3.33: The Export Icon
Reports can be saved in a variety of formats:
Table 3.4: File Formats

File Format Description
.rsrpt GTA Reporting Suite 2.0’s native file format.
.csv Comma Separated Value. This format can be opened in Microsoft Access
or Excel.
.html Hypertext Markup Language. Saves the report output as a web page.
.xml Extensible Markup Language.
.png Portable Network Graphics. Saves the report chart as a lossless image
suitable for presentations.
.jpg JPEG; Joint Photographic Experts Group. Saves the report chart as a
lossy image suitable for publishing online.
Figure 3.34: Exporting Reports
I m p o rt i n g Re p o rts
To load a previously exported report, select the Import icon or Import Report from the Reports menu.
Only reports exported as .rsrpt or .xml files can be opened by GTA Reporting Suite 2.0.
Figure 3.35: The Load Icon
Figure 3.36: Importing Reports
Reference A: User Interface
GTA Reporting Suite 2.0’s user interface remains consistent throughout the application. The main
menu contains general options while other, select options are available as clickable icons or by
using context-sensitive right-click menus.
Menu overview
The GTA Reporting Suite main window will display six main dropdown menus: File, View, Admin,
Reports, Window and Help.
Figure A.1: Menu Overview
File
The File menu contains the Exit command. Selecting Exit closes the application.
Figure A.2: File Menu
View
The View menu contains Locale, Firewall and User menu items. Locale provides a selection for the appli-
cation’s language. Firewall and User allow the administrator to change the method in which firewalls
and users are identified throughout the application.
Figure A.3: View Menu
GTA Reporting Suite 2.0 User’s Guide Reference A: User Interface 39

Admin
The Admin menu contains the Database Management menu item, which allows for the backup, purging
or restoration of the database. The Admin menu will only be visible to administrators organized
under the top-level (root) user group. For more information, please refer to the Database Manage-
ment section in Using GTA Reporting Suite 2.0.
Figure A.4: Admin Menu
Reports
The Reports menu allows for the importing of saved reports for review, re-running previously
performed reports, changing the report’s format, as well as printing and exporting reports.
Options are only available when they are relevant to the content displayed.
Figure A.5: Reports Menu
Window
The Window menu on the main menu bar contains the Close All command, which closes all open
reports.
Figure A.6: Window Menu
Help
To utilize online help for GTA Reporting Suite 2.0, see the Help Contents item. Find the version
number, date of the last build and the server the client is connected to in the About GTA Reporting Suite
dialog.
Figure A.7: Help Menu
40 GTA Reporting Suite 2.0 User’s Guide Reference A: User Interface

Action Buttons
The action buttons contain menu items associated with that topic. Available topics include Firewalls,
User Administration and Help.
Figure A.8: Action Buttons
Movable rulers
The vertical and horizontal movable rulers are used to resize or hide sections of the interface. For
instance, moving the horizontal ruler to the right will hide all open reports. Moving the ruler to the
left will hide the action buttons and their menus.
To quickly move the vertical or horizontal ruler to the edge of the screen, click the arrow pointing in
the direction you wish to move it. To resize a window within the application, drag the bar to where
you wish to place it.
Figure A.9: Movable Rulers

D r a g a n d D r o p Ta b s
To view open reports in a stand-alone window, click on the desired report’s tab at the top of the
report window and drag it to a new location on the screen. If the tab is dragged and dropped to
an unoccupied area of the screen a new window will be created to contain the report. Subsequent
tabs can be added to the new container window or they can be dragged to unoccupied areas to
create additional container windows. Tabs within container windows can also be dragged back
into the main GTA Reporting Suite 2.0 window. Container windows provide the same report
management functions as the main window.
Figure A.10: Before Dragging and Dropping a Tab
Figure A.11: After Dragging and Dropping a Tab

Standard Icons
The following icons are used throughout the GTA Reporting Suite 2.0 application.
Table A.1: Standard Icons

Icon Icon Value
Firewalls
Adds a firewall group to the Firewalls menu.
Adds a firewall to either the root (All) or a user defined group.
Deletes the selected firewall or group from the menu.
Opens the report menu for the selected firewall or group.
A configured firewall group.
An enabled firewall.
A disabled firewall.
Reports
Imports a previously saved report for reference or review.
Exports the selected report for future reference or review.
Changes the format of the report. For example, changing a report displayed as a pie chart to
display as a horizontal bar chart or as tabular text.
Prints the selected report to an installed printer on the client’s computer.
Runs or reruns the selected report.
User Administration
Adds a user group to the User Administration menu.
Adds a user to the selected group.
Deletes the selected user or group from the menu.
A user group.
An administrator or user.

Reference B: Reports
Charts and reports are listed in the order in which they appear in the Reports Menu. Chart
descriptions are based upon their default output.
Reports are broken down into the following categories:
• Usage Summary
• Security Policy Blocks
• Alarms
• Internet Access Management
• Mail Sentinel Reports
• Virus Summary
• Administrative Reports
Usage Summary
Usage Summary charts and reports display the number of bytes transferred between two
endpoints, or the total number of connections made to a URL.
B y S o u rc e IP A d d res s
Reports the total data transferred for the selected source IP address.
Table B.1: By Source IP Address

Input Prompt Source IP address, date/time range and Show Firewalls toggle
Columns Firewall*, Source IP Address, Bytes Received, Bytes Sent, Bytes Total
*This column is only displayed when the Show Firewalls toggle has been enabled.
B y D e s t i n atio n IP A d d re s s
Reports the total data transferred for the selected destination IP address.
Table B.2: By Destination IP Address

Input Prompt Destination IP address, date/time range and Show Firewalls toggle
Columns Firewall*, Destination IP Address, Bytes Received, Bytes Sent, Bytes Total
B y S o u rc e a n d Des tin a tio n IP Address

Reports the total data transferred for the selected source/destination IP address pair.
Table B.3: By Source and Destination IP Address

Input Prompt Source IP address, Destination IP address, date/time range and Show
Firewalls toggle
Columns Firewall*, Source IP Address, Destination IP Address, Bytes Received,
Bytes Sent, Bytes Total
GTA Reporting Suite 2.0 User’s Guide Reference B: Reports 45
B y P ro t o co l/De s tin a tio n Po rt and Source IP Address
Reports the total data transferred for the selected protocol/destination port and source IP address
pair.
Table B.4: By Protocol/Destination Port and Source IP Address

Input Prompt Source IP address, protocol, destination port, date/time range and Show
Firewalls toggle
Columns Firewall, Protocol, Destination Port, Source IP Address, Bytes Received,
Bytes Sent, Bytes Total
B y P ro t o co l/De s tin a tio n Po rt and Dest inat ion IP Address

Reports the total data transferred for the selected protocol/destination port and source IP address
pair.
Table B.5: By Protocol/Destination Port and Destination IP Address

Input Prompt Destination IP address, protocol, destination port, date/time range and
Show Firewalls toggle
Columns Firewall*, Protocol, Destination Port, Destination IP Address, Bytes
Received, Bytes Sent, Bytes Total
B y Ti me , Da y a n d S o u rc e IP Address
Plots the total data transferred for the selected source IP address by time and day.
Table B.6: By Time, Day and Source IP Address

Input Prompt Source IP address and date/time range
Description Line graph with usage (vertical) by hour (horizontal) with color coded plot
points for days
B y Ti me , Da y a n d Des tin a tion IP Address

Plots the total data transferred for the selected destination IP address by time and day.
Table B.7: By Time, Day and Destination IP Address

Input Prompt Destination IP address and date/time range
Description Line graph with usage (vertical) by hour (horizontal) with color coded plot
points for days
46 GTA Reporting Suite 2.0 User’s Guide Reference B: Reports

B y Ti me an d S o u rce IP A d d ress
Charts the total data transferred for the selected source IP address by time.
Table B.8: By Time and Source IP Address

Description Bar chart with usage (vertical) by hour (horizontal)
B y Ti me an d De s tin a tio n IP Address

Charts the total data transferred for the selected destination IP address by time.
Table B.9: By Time and Destination IP Address

Description Bar chart with usage (vertical) by hour (horizontal)
B y D a y o f We e k a n d S o u rc e IP Address
Charts the total data transferred for the selected source IP address by the day of the week.
Table B.10: By Day of Week and Source IP Address

Input Prompt Source IP address and date range
Description Bar chart with usage (vertical) by day of week (horizontal)
B y D a y o f We e k a n d Des tin at ion IP Address

Charts the total data transferred for the selected destination IP address by the day of the week.
Table B.11: By Day of Week and Destination IP Address

Input Prompt Destination IP address and date range
Description Bar chart with usage (vertical) by day of week (horizontal)
“ To p 1 0 ” R e p o r t s
“Top 10” Reports contains charts of the top ten highest rates of use for the selected report
category.
Charts the total data transferred for the source IP addresses with the top ten highest rates of use.

Description Horizontal bar chart with usage (horizontal) for each firewall*/source IP
address (vertical)
*The firewall is only displayed when the Show Firewalls toggle has been enabled.

Charts the total data transferred for the destination IP addresses with the top ten highest rates of
use.

Description Horizontal bar chart with usage (horizontal) for each firewall*/destination IP
address (vertical)
B y S o u rc e a n d Des tin a tio n IP Address

Charts the total data transferred for the source/destination IP address pairs with the top ten
highest rates of use.
Table B.14: By Source and Destination IP Address

Input Prompt Source IP address, destination IP address, date/time range and Show
Firewalls toggle
Description Horizontal bar chart with usage (horizontal) for each firewall*/source/desti-
nation IP address pair (vertical)
B y P ro t o co l/De s tin a tio n Po rt and Source IP Address

Charts the total data transferred for the selected protocol/destination port and source IP address
pairs with the top ten highest rates of use.
Table B.15: By Protocol/Destination Port and Source IP Address

Firewalls toggle
Description Horizontal bar chart with usage (horizontal) for each firewall*/protocol/
destination port and source IP address (vertical)
B y P ro t o co l/De s tin a tio n Po rt and Dest inat ion IP Address

Charts the total data transferred for the selected protocol/destination port and source IP address
pairs with the top ten highest rates of use.
Table B.16: By Protocol/Destination Port and Destination IP Address

Input Prompt Destination IP address, protocol, destination port, date/time range and
Show Firewalls toggle
Columns Horizontal bar chart with usage (horizontal) for each firewall*/protocol/
destination port and destination IP address (vertical)

Security Policy Blocks
Security Policy Blocks summarizes the number of packets blocked by a security policy.
B y S o u r ce IP Address
Reports the total number of security policy blocks by policy type for the source IP address.

Columns Firewall*, Source IP Address, Policy Type, Blocks
Reports the total number of security policy blocks by policy type for the destination IP address.

Columns Firewall*, Destination IP Address, Policy Type, Blocks
Charts the total number of security policy blocks by the day of the week for the source IP address.

Input Prompt Source IP address and date range
Description Horizontal bar chart with blocks (horizontal) for each day of the week (verti-
cal)

Charts the total number of security policy blocks by the day of the week for the destination IP
address.

Input Prompt Destination IP address and date range
Description Horizontal bar chart with blocks (horizontal) for each day of the week (verti-
cal)

Plots the total number of security policy blocks by time and day for the source IP address.

Description Line graph with blocks (horizontal) for each hour (vertical) with color coded
plot points for days

Plots the total number of security policy blocks by time and day for the destination IP address.

Description Line graph with blocks (horizontal) for each hour (vertical)
Charts the total number of security policy blocks by time of day for the source IP address.

Description Horizontal bar chart with blocks (horizontal) for each hour (vertical)

Charts the total number of security policy blocks by time of day for the destination IP address.

Description Horizontal bar chart with blocks (horizontal) for each hour (vertical)
B y S o u rc e A d d re s s , S o u rc e Port and Prot ocol

Reports the total number of security policy blocks for the source IP address and associated
source ports, protocols and policy types.
Table B.25: By Source Address, Source Port and Protocol

Input Prompt Source IP address, protocol, source port, date/time range and Show
Firewalls toggle
Columns Firewall*, Source IP Address, Protocol, Source Port, Policy Type, Blocks

B y S o u rc e A d d re s s , Des tin at ion Port and Prot ocol
Reports the total number of security policy blocks for the source IP address and associated desti-
nation ports, protocols and policy types.
Table B.26: By Source Address, Destination Port and Protocol

Firewalls toggle
Columns Firewall*, Source IP Address, Protocol, Destination Port, Policy Type,
Blocks
P o l i c i e s Trig g e re d b y S o u rce IP Address

Reports the total number of security policy blocks for each rule violated by source IP address.
Table B.27: Rules Triggered by Source IP Address
Columns Firewall*, Policy, Policy Type, Source IP Address, Blocks
P o l i c i e s Trig g e re d b y Des tinat ion IP Address

Reports the total number of security policy blocks for each rule violated by destination IP
addresses.
Table B.28: Rules Triggered by Destination IP Address

Columns Firewall*, Policy, Policy Type, Destination IP Address, Blocks
To t a l P o l ic ie s Trig g e re d
Reports the total number of security policy blocks for each rule violated.
Table B.29: Total Rules Triggered

Input Prompt Date/time range and Show Firewalls toggle
Columns Firewall*, Policy, Policy Type, Blocks

“ To p 1 0 ” R e p o r t s
category.
Charts the total number of security policy blocks for the source IP addresses with the top ten

Description Horizontal bar chart with usage (horizontal) for each firewall*/source IP
address/policy type (vertical)
Charts the total number of security policy blocks for the destination IP addresses with the top ten

Description Horizontal bar chart with blocks (horizontal) for each firewall*/destination IP
address/policy type (vertical)
B y S o u rc e A d d re s s , Des tin at ion Port and Prot ocol

Charts the total number of security policy blocks for the source IP addresses with the top ten
Table B.32: By Source Address, Destination Port and Protocol

Firewalls toggle
Description Horizontal bar chart with blocks (horizontal) for each firewall*/source IP
address/protocol/policy type (vertical)
P o l i c i e s Trig g e re d b y S o u rce IP Address

Charts the top ten total number of security policy blocks by source IP addresses for each rule
violated.
Table B.33: Rules Triggered by Source IP Address

Description Horizontal bar chart with blocks (horizontal) for each firewall*/policy/policy
type/source IP address (vertical)

P o l i c i e s Trig g e re d b y Des tinat ion IP Address
Charts the top ten total number of security policy blocks with the top ten highest rates of use by
destination IP addresses for each rule violated.
Table B.34: Rules Triggered by Destination IP Address
Description Horizontal bar chart with blocks (horizontal) for each firewall*/policy/policy
type/destination IP address (vertical)
To t a l P o l ic ie s Trig g e re d
Charts the top ten total number of security policy blocks by each rule violated.
Table B.35: Total Policies Triggered

Description Vertical bar chart with blocks (vertical) for each firewall*/policy/policy type
(horizontal)
B y S o u rc e A d d re s s , S o u rc e Port and Prot ocol

Charts the total number of security policy blocks for the source IP address and associated source
ports, protocols and policy types.
Table B.36: By Source Port

Input Prompt Source IP address, protocol, source port, date/time range and Show
Firewalls toggle
Description Horizontal bar chart with blocks (horizontal) for each firewall*/source IP
address/protocol/source port/policy type (vertical)

Alarms
Alarms summarizes alarm reports.
Plots the total alarms caused by the specified IP address or addresses for each hour of the day
and day of the week.

Description Line graph with the number of alarms (vertical) by each hour (horizontal)
with color coded plot points for days
P o l i c y A l arms Trig g e re d b y Source IP Address

Report of the total policy alarms triggered by each source IP address.
Table B.38: Policy Alarms Triggered by Source IP Address

Columns Firewall*, Policy, Policy Type, Source IP Address, Count
P o l i c y A l arms Trig g e re d b y Dest inat ion IP Address

Report of the total policy alarms triggered by each destination IP address.
Table B.39: Policy Alarms Triggered by Destination IP Address

Columns Firewall*, Policy, Policy Type, Destination IP Address, Count
To t a l P o l ic y A la rms Trig g e red

Report of the total number of times each policy alarm has been triggered. Zero counts are not
reported.
Table B.40: Total Policy Alarms Triggered

Columns Firewall*, Policy, Policy Type, Alarms

A l a rms b y Des tin a tio n IP A ddress
Report of alarms showing the firewall, alarm type, policy type, destination IP address and alarm
count.
Table B.41: Alarms by Destination IP Address

Columns Firewall*, Alarm Type, Policy Type, Destination IP Address, Alarms
A l a rms b y Des tin a tio n Po rt

Report of alarms showing the firewall, alarm type, policy type, protocol, destination port and alarm
count.
Table B.42: Alarms by Destination Port

Input Prompt Protocol, destination port, date/time range and Show Firewalls toggle
Columns Firewall*, Alarm Type, Policy Type, Protocol, Destination Port, Alarms
A l a rms b y S o u rc e IP A d d re ss
Report of alarms showing the firewall, alarm type, policy type, source IP address and alarm count.
Table B.43: Alarms by Source IP Address

Columns Firewall*, Alarm Type, Policy Type, Source IP Address, Alarms
A l a rms b y S o u rc e Po rt
Report of alarms showing the firewall, alarm type, policy type, protocol, source port and alarm
count.
Table B.44: Alarms by Source Port

Input Prompt Protocol, source port, date/time range and Show Firewalls toggle
Columns Firewall*, Alarm Type, Policy Type, Protocol, Source Port, Alarms
Charts the total alarms for each day of the week for specified source IP address.

Description Horizontal bar chart with the total number of alarms (horizontal) for each
day of the week (vertical)

Charts the total alarms for each day of the week for specified destination IP address.

day of the week (vertical)
Charts the total alarms for each hour of the day for specified source IP address.

hour of the day (vertical)

Charts the total alarms for each hour of the day for specified destination IP address.

hour of the day (vertical)

Plots the total alarms for the specified IP address or addresses for each hour of the day and day of
the week.

Description Line graph with the total number of alarms (vertical) or each hour of the day
(horizontal) with color coded plot points for days

“ To p 1 0 ” R e p o r t s
“Top 10” Reports contains charts of the top ten alarms for the selected category.
A l a rms b y Des tin a tio n IP A ddress

Chart of the top ten alarms showing the firewall, alarm type, policy type, destination IP address
and alarm count.
Table B.50: Alarms by Destination IP Address

Description Horizontal bar chart with alarms (horizontal) by firewall*/alarm type/policy
type/destination IP address (vertical)
A l a rms b y Des tin a tio n Po rt

Chart of the top ten alarms showing the firewall, alarm type, policy type, destination port and
alarm count.
Table B.51: Alarms by Destination Port

Input Prompt Protocol, destination port, date/time range and Show Firewalls toggle
type/protocol/destination port (vertical)
A l a rms b y S o u rc e IP A d d re ss
Chart of the top ten alarms showing the firewall, alarm type, policy type, source IP address and
alarm count.
Table B.52: Alarms by Source IP Address

type/source IP address (vertical)
A l a rms b y S o u rc e Po rt
Chart of the top ten alarms showing the firewall, alarm type, policy type, source port and alarm
count.
Table B.53: Alarms by Source Port

Input Prompt Protocol, source port, date/time range and Show Firewalls toggle
type/protocol/source port (vertical)

P o l i c y A l arms Trig g e re d b y Source IP Address
Chart of the top ten total alarms triggered by each source IP address.
Table B.54: Policy Alarms Triggered by Source IP Address

Description Horizontal bar chart with the number of alarms triggered (horizontal) for
each firewall*/policy/policy type/source IP address (vertical)
P o l i c y A l arms Trig g e re d b y Dest inat ion IP Address

Chart of the top ten total alarms triggered by each destination IP address.
Table B.55: Policy Alarms Triggered by Destination IP Address

Description Horizontal bar chart with the number of alarms triggered (horizontal) for
each firewall*/policy/policy type/destination IP address (vertical)
To t a l P o l ic y A la rms Trig g e red

Chart of the top ten total alarms triggered.
Table B.56: Total Policy Alarms Triggered

Description Vertical bar chart with the number of alarms triggered (vertical) for each
firewall*/policy/policy type (horizontal)
Internet Access Management

Internet Access Management displays information gathered through content filtering. Reports
organized under Surf Sentinel Reports are only available to those with valid Surf Sentinel
subscriptions.
A 30 day evaluation of Surf Sentinel can be requested from GTA’s website at http://www.gta.com/
options/contFilterDemo/.
M o s t - Vi s ite d URLs b y Use r IP Address

Reports the most visited URLs by user IP address.
Table B.57: Most Visited URLs

Input Prompt User IP address, date/time range
Columns User IP Address, Connections, URL

We b U s a ge S u mmary b y User IP Address and URL
Reports the total bytes transferred to and from each pair of user IP addresses and URLs.
Table B.58: Web Usage Summary by User IP Address and URL

Input Prompt User IP Address, date/time range
Columns User IP Address, Connections, Bytes Received, Bytes Sent, Bytes Total,
URL
URL s b y B an d wid th
Reports the amount of bandwidth used by each URL. This report is useful if you wish to view
detailed traffic reports for your internal web server.
Table B.59: URLs by Bandwidth

Input Prompt Date/time range, site, page and Show Page toggle
Columns Bytes Received, Bytes Sent, Bytes Total, Site, Page*
*This column is only displayed when the Show Page toggle has been enabled.
To t a l C o nn ec tio n s b y Time , Day and User IP Address

Plots the total connections by hour, day and user IP address.
Table B.60: Total Connections by Time, Day and User IP Address

Description Line graph with connections (vertical) for each hour (horizontal) with color
coded plot points for days
We b U s e r s b y Co n n e c tio n s
Reports the total number of web users by connection. Requires authentication.
Table B.61: Web Users by Connection

Input Prompt Date/time range
Columns User Name*, User IP Address, Total
*User names are displayed only if users authenticated via GBAuth.
URL s b y B an d wid th an d User IP Address

Reports the total bandwidth used by user IP address per URL.
Table B.62: URLs by Bandwidth and User IP Address

Columns User IP Address, Bytes Received, Bytes Sent, Bytes Total, URL

We b A c c es s Details b y Use r, Web Sit e and Web Page
Reports web access by URL.
Table B.63: Web Access Details by User, Web Site and Web Page
Input Prompt Date/time range, user IP address, user name. site, page and Show User
Names toggle
Columns Time, User IP Address, User Name*, Site, Page
*This column is only displayed when the Show User Names toggle has been enabled. User names are displayed only if
users authenticated via GBAuth.
B l o c k e d We b A cc e s s A tte mpt s by Time, Day and User IP Address

Plots the total blocked web access attempts by time and user IP address.
Table B.64: Blocked Web Access Attempts by Time, Day and User IP Address
Columns Line graph with blocked access attempts (vertical) for each hour (horizon-
tal) with color coded plot points for days
“ To p 1 0 ” R e p o r t s
category.
M o s t - Vi s ite d URLs b y Use r IP Address

Charts the top ten total most visited URLs by number of connections.
Table B.65: Most Visited URLs by User IP Address

Description Horizontal bar chart with total connections (horizontal) for each user IP
address/URL (vertical)
URL s b y B an d wid th
Charts the top ten URLs by bandwidth usage .
Table B.66: URLs by Bandwidth

Description Horizontal bar chart with bandwidth (horizontal) used for each URL (verti-
cal)

We b U s e r s b y Co n n e c tio n s
Charts the top ten web users by the number of connections.
Table B.67: Web Users by Connection

Description Horizontal bar chart with connections (horizontal) made by each user
name*/user IP address (vertical)
URL s b y B an d wid th an d User IP Address

Charts the top ten URLs and User IP addresses by bandwidth used.
Table B.68: URLs by Bandwidth and User IP Address

Description Horizontal bar chart with bandwidth used (horizontal) by each user IP
Surf Sentinel Reports

Surf Sentinel Reports are only available to those with a valid Surf Sentinel subscription. A 30-day
evaluation of Surf Sentinel can be requested from GTA’s website at http://www.gta.com/options/
contFilterDemo/.
To t a l A c ce s s A tte mp ts b y User Name

Reports the total access attempts by user name. Requires Surf Sentinel and authentication.
Table B.69: Total Access Attempts by User Name

Input Prompt User Name, date/time range
Columns User Name, Destination IP Address, Web Site, Category, Total Attempts
To t a l A c ce s s A tte mp ts b y User Name, IP Address and URL

Reports the total access attempts made by user name, IP address and URL. Requires Surf
Sentinel and authentication.
Table B.70: Total Access Attempts by User Name, IP Address and URL
Input Prompt User Name, User IP Address, URL, date/time range
Columns User Name, User IP Address, Time, Web Site

To t a l B l o cke d We b A cc e s s At t empt s by Cat egory
Reports the total blocked access attempts made by category. Requires Surf Sentinel.
Table B.71: Total Blocked Web Access Attempts by Category

Columns Category, Blocks
B l o c k e d We b A cc e s s A tte mpt s by Time and User IP Address

Reports the total blocked access attempts made by time and user IP address. Requires Surf
Sentinel.
Table B.72: Blocked Web Access Attempts by Time and IP Address

Input Prompt User IP Address, Date/time range
Columns Time, User IP Address, Web Site, Category
B l o c k e d We b A cc e s s A tte mpt s by Time and User IP Address

Plots the total blocked access attempts made by time and user IP address. Requires Surf
Sentinel.
Table B.73: Total Blocked Web Access Attempts by Time and IP Address
Input Prompt User IP Address, Date/time range
Description Line graph with blocked access attempts (horizontal) for each hour (verti-
cal) with color coded plot points for days
B l o c k e d We b A cc e s s A tte mpt s by Time and User Name

Reports the total blocked access attempts made by time and user name. Requires Surf Sentinel.

Columns Time, User Name*, User IP Address, Web Site, Category
B l o c k e d We b A cc e s s A tte mpt s by Time and User Name

Plots the total blocked access attempts made by time and user name. Requires Surf Sentinel.

Description Line graph with blocked access attempts (horizontal) for each hour (verti-
cal) with color coded plot points for days

B l o c k e d We b A cc e s s A tte mpt s by User IP Address
Reports the total blocked access attempts made by user IP address. Requires Surf Sentinel.
Table B.76: Blocked Web Access Attempts by User IP Address

Columns User IP Address, Web Site, Category, Blocks
B l o c k e d We b A cc e s s A tte mpt s by User Name

Reports the total blocked access attempts made by user name. Requires Surf Sentinel.
Table B.77: Blocked Web Access Attempts by User Name

Input Prompt User name, date/time range
Columns User Name*, User IP Address, Web Site, Category, Blocks
C o n n e c t io n s b y Web Ca teg ory

Reports the total web connections to each web category. Requires Surf Sentinel.
Table B.78: Connections by Category

Columns Category, Connections
We b U s a ge S u mmary b y Cat egory and Dest inat ion IP Address

Reports the total bytes transferred to and from each web category and destination address.
Requires Surf Sentinel.
Table B.79: Web Usage Summary by Category and Destination IP Address

Columns Category, Connections, Bytes Received, Bytes Sent, Bytes Total,
Destination IP Address
We b U s a ge S u mmary b y Cat egory and URL

Reports the total bytes transferred to and from each web category and URL. Requires Surf
Sentinel.
Table B.80: Web Usage Summary by Category and URL

Columns Category, Connections, Bytes Received, Bytes Sent, Bytes Total, URL

We b U s a ge S u mmary b y Cat egory
Reports the total bytes transferred to and from each web category. Requires Surf Sentinel.
Table B.81: Web Usage Summary by Category

Columns Category, Connections, Bytes Received, Bytes Sent, Bytes Total
We b C a t eg o rie s b y B an d widt h
Reports the amount of bandwidth used by each web category. Requires Surf Sentinel.
Table B.82: Web Categories by Bandwidth

Columns Category, Connections, Bytes Received, Bytes Sent, Bytes Total
“ To p 1 0 ” R e p o r t s
Surf Sentinel “Top 10” Reports are only available to those with a valid Surf Sentinel subscription.
A 30-day evaluation of Surf Sentinel can be requested from GTA’s website at http://www.gta.com/
options/contFilterDemo/.
category.
To t a l A c c e s s A tte mp ts b y User Name

Charts the top ten total access attempts by user name. Requires Surf Sentinel and authentication.
Table B.83: Total Access Attempts by User Name

Description Horizontal bar chart with total access attempts (horizontal) for each user
name/destination IP address/web site/category (vertical)
To t a l B l o ck e d We b A cc e s s At t empt s by Cat egory

Charts the top ten total number of blocked web access attempts by category. Requires Surf
Sentinel.
Table B.84: Total Blocked Web Access Attempts by Category

Description Horizontal bar chart with total blocked web access attempts (horizontal) for
each category (vertical)

B l o c k e d We b A cc e s s A tte mpt s by User IP Address
Sentinel.
Table B.85: Total Blocked Web Access Attempts by User IP Address

each user IP address/web site/category (vertical)
B l o c k e d We b A cc e s s A tte mpt s by User Name

Sentinel.
Table B.86: Blocked Web Access Attempts by User Name

each user name*/user IP address/web site/category (vertical)
C o n n e c t i o n s b y Web Ca teg ory

Charts the top ten total number of number of connections to each web category. Requires Surf
Sentinel.
Table B.87: Connections to Web Category

Description Horizontal bar chart with total connections (horizontal) for each web cat-
egory (vertical)
We b U s a ge S u mmary b y Cat egory and Dest inat ion IP Address

Charts the top ten total usage by category and destination IP address. Requires Surf Sentinel.
Table B.88: Web Usage Summary by Category and Destination IP Address

Description Horizontal bar chart with usage (horizontal) for each category/destination
IP address (vertical)
We b U s a ge S u mmary b y Cat egory and URL

Charts the top ten total usage by category and destination IP address. Requires Surf Sentinel.
Table B.89: Web Usage Summary by Category and URL

Description Horizontal bar chart with usage (horizontal) for each category/URL (vertical)

We b C o n nec tio n s b y Categ ory and URL
Charts the top ten total web connections by category and URL. Requires Surf Sentinel.

Description Horizontal bar chart with connections (horizontal) for each category/URL
(vertical)
We b U s a ge S u mmary b y Cat egory

Charts the top ten total usage by category. Requires Surf Sentinel.

Description Horizontal bar chart with usage (horizontal) for each category (vertical)
We b C o n nec tio n s b y Categ ory

Charts the top ten total connections by category. Requires Surf Sentinel.

Description Horizontal bar chart with connections (horizontal) for each category (verti-
cal)
We b C a t e g o rie s b y B an d widt h
Charts the top ten total usage by category and bandwidth used. Requires Surf Sentinel.

Description Horizontal bar chart with usage (horizontal) for each category (vertical)
We b U s a ge S u mmary b y User IP Address and URL

Charts the top ten User IP addresses and URLs by web usage. Requires Surf Sentinel.

Description Horizontal bar chart with bandwidth used (horizontal) by each user IP

We b C o n nec tio n s b y Use r IP Address and URL
Charts the top ten User IP addresses and URLs by web usage. Requires Surf Sentinel.

Description Horizontal bar chart with total connections (horizontal) by each user IP
Mail Sentinel Reports

Mail Sentinel Reports summarize email reports generated by the Mail Sentinel proxy.
E ma i l D i sp o s itio n S u mma ry
Report of the amount of email and classification. Requires Mail Sentinel proxy.
Table B.96: Email Disposition Summary

Columns Action, Message, Count
E ma i l D i sp o s itio n S u mma ry
Chart of the amount of email and classification. Requires Mail Sentinel proxy.
Table B.97: Email Disposition Summary

Description Pie chart showing action, message and count
E ma i l P a ss /B lo c k S u mmary
Chart of the amount of email passed and blocked. Requires Mail Sentinel proxy.
Table B.98: Email Pass/Block Summary

Description Pie chart showing action and count

Mail Sentinel Anti-Virus Reports
Mail Sentinel Anti-Virus Reports contain charts and reports generated by Mail Sentinel Anti-
Virus. Mail Sentinel Anti-Virus Reports are only available to those with a valid Mail Sentinel
Anti-Virus subscription. A 30-day evaluation of Mail Sentinel Anti-Virus can be requested from
GTA’s website at http://www.gta.com/options/mailSentinelDemoChoice/
Vi ru s Su m ma ry
Chart of the viruses detected and the number of times each virus was detected. Requires Mail
Sentinel Anti-Virus.
Table B.99: Virus Summary

Description Pie chart showing virus names and count
Vi ru s O rig in ato rs
Report of virus originators showing the virus, user name, user IP address and the number of times
each virus was detected. Requires Mail Sentinel Anti-Virus.
Table B.100: Virus Originators

Columns Virus, User, User IP Address, Count
Vi r u s D e tails
Report of viruses detected showing the date, virus, user name and user IP address. Requires Mail
Sentinel Anti-Virus.
Table B.101: Virus Details

Columns Time, Virus, User, User IP Address
“ To p 1 0 ” R e p o r t s
“Top 10” Reports charts the top ten counts for the selected category.
Vi ru s O rig in ato rs
Chart of the top ten virus originators showing the user name, IP address and number of viruses
detected. Requires Mail Sentinel Anti-Virus.
Table B.102: Virus Originators

Description Horizontal bar chart with count (horizontal) by user name/user IP address
(vertical)

Mail Sentinel Anti-Spam Reports
Mail Sentinel Anti-Spam Reports contain charts and reports generated by Mail Sentinel Anti-
Spam. Mail Sentinel Anti-Spam Reports are only available to those with a valid Mail Sentinel
Anti-Virus subscription. An evaluation of Mail Sentinel Anti-Spam can be requested from GTA’s
website at http://www.gta.com/options/mailSentinelDemoChoice/
S p a m D i s p o s itio n S u mma ry
Report of the amount of spam and its disposition. Requires Mail Sentinel Anti-Spam.
Table B.103: Spam Disposition Summary

Columns Action, Disposition, Count
S p a m D i s p o s itio n S u mma ry
Chart of the amount of spam and its disposition. Requires Mail Sentinel Anti-Spam.
Table B.104: Spam Disposition Summary

Description Pie chart showing action, disposition and count
B l o c k e d S p a m Details
Report of blocked email messages showing the time, spam disposition, confidence score, origi-
nating user and originating user IP address. Requires Mail Sentinel Anti-Spam.
Table B.105: Blocked Spam Details

Columns Time, Disposition/Score, Originating User, User IP Address

Administrative Reports
Administrative Reports summarizes miscellaneous administrative activities.
Note
Administrative Reports are only available to users with permissions set to Administrator.
F W CC A d m i n i s t r a t i v e R e p o r t s
Firewall Control Center Administrative Reports contains miscellaneous GTA Reporting Suite
2.0 administrative reports. Reports contained in this category are only available to top-level
administrators.
U s e r L o g o n /Lo g o ff A c tivity
Report of the date, time and action of GTA Reporting Suite 2.0 user logon/logoff activity.
Table B.105: User Logon/Logoff Activity

Columns Time, User Name*, Action
*Displayed user names are those used to logon to GTA Reporting Suite 2.0 and are not used for authenticating via GBAuth.
R e p o rt i n g A c tivity
Report of the reports run by the selected GTA Reporting Suite 2.0 user(s) during the selected time
period.
Table B.106: Reporting Activity

Input Prompt User Name*, date/time range
Columns Time, User Name*, Menu ID, Report Title
U s e r M a i nte n an ce A c tivity
Report of GTA Reporting Suite 2.0 users added, deleted or modified during the selected time
period.
Table B.107: User Maintenance Activity

Columns Time, User Name*, Type, Action

F i re w a l l Main te n an ce A c tivit y
Report of firewalls added, deleted or modified during the selected time period.
Table B.108: User Logon/Logoff Activity

Columns Time, User Name*, Type, Action
Firewall Administrative Reports

Firewall Administrative Reports contains miscellaneous firewall administrative reports.
R a w L o g Rep o rts
Raw log reports generated by the firewall. Entering a search string filters the results.
Table B.109: Raw Log Reports

Input Prompt Date/time range and text search
Columns Raw log reports.

Reference C: Creating DSNs
GTA Reporting Suite 2.0 requires DSNs (Data Source Names) to be defined on servers that
are operating as the Database Backend. When installing the Database Backend on Microsoft
Windows, the option is available to allow the installer to create the necessary DSNs automatically.
Linux installations of the Database Backend require that DSNs be manually defined.
Microsoft Windows
During the installation process, you will be prompted to create DSNs (Data Source Names).
Although the GTA Reporting Suite 2.0 installer can generate the required DSNs automatically, the
option is available to create them manually.
The DSNs can be created using either MySQL, PostgreSQL or Microsoft SQL Server.
Note
Illustrations are used as an example only. Displayed values in the Host/Server Name (or IP) and Server
fields may not apply to your configuration.
Creating DSNs Using MySQL

To create the DSNs using MySQL, use the following information:
Firewall Control Center DSN Configuration

Field Name Field Value
Data Source name FWCC
Descriptions DSN for the Firewall Control Center
Host/Server Name Name or IP address of the database management server
Database Name gta_firewall
User fwcc
Password fwccpwd
Port 3306
Figure C.1: Creating the Firewall Control Center DSN Using MySQL
GTA Reporting Suite 2.0 User’s Guide Reference C: Creating DSNs 73

Firewall Control Center Admin DSN Configuration
Data Source name FWCC Admin
Description Administration DSN for the Firewall Control Center
Host/Server Name Name or IP address of the database management server
Database Name mysql
User Administrator’s user name
Password Administrator’s password, if any
Port 3306
Figure C.2: Creating the Firewall Control Center Admin DSN Using MySQL
Creating DSNs Using PostgreSQL

To create the DSNs using PostgreSQL, use the following information:
Firewall Control Center DSN Configuration

Data Source FWCC
Description DSN for the Firewall Control Center
Database gta_firewall
Server Name or IP address of the database management server
User Name fwcc
Password fwccpwd
Port 5432
Figure C.3: Creating the Firewall Control Center DSN Using PostgreSQL
74 GTA Reporting Suite 2.0 User’s Guide Reference C: Creating DSNs

Firewall Control Center Admin DSN Configuration
Data Source FWCC Admin
Description Administration DSN for the Firewall Control Center
Database template1
Server Name or IP address of the database management server
User Name postgres (User defined in database install)
Password <Enter password, if any>
Port 5432
Figure C.4: Creating the Firewall Control Center Admin DSN Using PostgreSQL
Creating DSNs Using MS SQL Server

To create the DSNs using Microsoft SQL Server, navigate to the Control Panel, select Administra-
tive Tools and the open the Data Sources (ODBC) application.
C re a t i n g th e F irewa ll Co n trol Cent er DSN

Select the System DSN Tab.
Figure C.5: System DSN

Click the Add button to create the new System DSN. You will be prompted with the Create New
Data Source screen. Select SQL Server and click Finish.
Figure C.6: Creating the New Data Source
Clicking Finish will start the Microsoft SQL Server DSN Configuration wizard. Enter the following
information:
Name: FWCC
Server: Name or IP address of the database management server
If you are using an instance name, append the instance name to the end of the server’s name or IP
address (e.g., localhost/GTAFWCC)
Click Next.
Figure C.7: Name and Server Information

The next screen will configure login authentication. Select With SQL Server Authentication..., then
check Connect to SQL Server... and enter the following information:
Login: fwcc
Password: fwccpwd
Figure C.8: Login Authentication
Next, un-check Connect to SQL Server... and click Next.
Figure C.9: Un-checking Connect to SQL Server...
The next screen will configure database settings. Select Change the default database to: and enter
“gta_firewall” (without quotes).
Ignore all other options and click Next.
Figure C.10: Changing the Default Database

Ignore the options on the final screen and click Finish to complete the wizard.
Figure C.11: Completing the Wizard
C re a t i n g th e F irewa ll Co n trol Cent er Admin DSN

Select the System DSN Tab and click the Add button.
Figure C.12: System DSN
You will be prompted with the Create New Data Source screen. Select SQL Server and click Finish.
Figure C.13: Creating the New Data Source

Clicking Finish will start the Microsoft SQL Server DSN Configuration wizard. Enter the following
information:
Name: FWCC Admin
Server: Name or IP address of the database management server
If you are using an instance name, append the instance name to the end of the server’s name or IP
address (e.g., localhost/GTAFWCC)
Click Next.
Figure C.14: Name and Server Information
The next screen will configure login authentication. Select With SQL Server Authentication..., then
check Connect to SQL Server... and enter the following information:
Login: sa
Password: <Enter Configured Password>
Figure C.15: Login Authentication
Optionally, you may un-check Connect to SQL Server.... Click Next.

The next screen will configure database settings. Select Change the default database to: and enter
“master” (without quotes).
Ignore the other options and click Next.
Figure C.16: Changing the Default Database
Ignore the options on the final screen and click Finish to complete the wizard.
Figure C.17: Completing the Wizard

Linux
It is assumed that the database’s software package and unixODBC have been installed. For
instructions on installing and configuring the database’s software package, refer to the software
package’s documentation.
C r e a t i n g a n OD B C D r i v e r
Before the DSNs for the GTA Reporting Suite 2.0 Database Backend can be defined, it may
be necessary to define an ODBC driver for use with the selected database software package.
Existing ODBC drivers can be listed by opening the Terminal application and entering the following
command:
odbcinst -q -d
If the ODBC driver for the selected database software package is not shown then it will be neces-
sary to define a driver. See Defining an ODBC Driver for MySQL or Defining an ODBC Driver for
PostgreSQL, as appropriate. If a suitable driver appears in the list then see Creating DSNs Using
MySQL or Creating DSNs Using PostgreSQL, as appropriate.
D e f i n i n g an OD B C Drive r fo r M ySQL
To create the driver template file for use with MySQL, enter the following into the
odbcinst_template.ini file. Note that the text contained within the brackets is the driver name that
will be used by the DSN.
[MySQL]
Description = MySQL ODBC driver
Driver = /usr/lib/libmyodbc3.so
Setup = /usr/lib/libmyodbc3S.so
Save the odbcinst_template.ini file and close the text editor. Next, the driver must be installed. To
do so, see Installing the ODBC Driver.
D e f i n i n g an OD B C Drive r fo r Post greSQL

To create the driver template file for use with PostgreSQL, enter the following into the
odbcinst_template.ini file. Note that the text contained within the brackets is the driver name that
will be used by the DSN.
[PostgreSQL]
Description = PostgreSQL ODBC driver
Driver = /usr/lib/libodbcpsql.so
Setup = /usr/lib/libodbcpsqlS.so
Save the odbcinst_template.ini file and close the text editor. Next, the driver must be installed. To
do so, see Installing the ODBC Driver.
I n s t a l l i n g th e OD B C Driv e r
To install the ODBC driver, open Terminal and enter the following command:
odbcinst -i -d -f <pathname of odbcinst_template.ini>
Next, the DSNs for the selected database software package must be created.

Creating DSNs Using MySQL
To create the template file for use with MySQL, enter the following into the
odbcinst_template.ini file. The MySQL driver name must match one of the names displayed when
the odbc_template.ini -q -d command is run in Terminal, or match the name entered into the
odbcinst_template.ini file. Text contained within the brackets are the data source names.
[FWCC]
Driver = <MySQL driver name>
Database = gta_firewall
Description = FWCC Database
Option = 2
Port = 3306
Server = <IP address or DNS resolvable host name>
UID = fwcc
PWD = fwccpwd
[FWCC Admin]
Driver = <MySQL driver name>
Database = mysql
Description = FWCC Administrative Database
Option = 2
Port = 3306
Server = <IP address or DNS resolvable host name>
UID = root
PWD = <password defined for MySQL root user>
Save the odbc_template.ini and close the text editor. Next, the DSN must be installed.
I n s t a l l i n g th e DS N
Open the Terminal application and enter the following:
odbcinst -i -s -l -f <pathname of odbc_template.ini>
Close the Terminal application. Installation of the DSNs necessary for the GTA Reporting Suite 2.0
Database Backend is now complete.

Creating DSNs Using PostgreSQL
To create the template file for use with PostgreSQL, enter the following into the
odbc_template.ini file. The PostgreSQL driver name must match one of the names displayed
when the odbc_template.ini -q -d command is run in Terminal, or match the name entered
into the odbcinst_template.ini file. Text contained within the brackets are the data source names.
[FWCC]
Driver = <PostgreSQL driver name>
Database = gta_firewall
Description = FWCC Database
Options =
Port = 5432
Servername = <IP address or DNS resolvable host name>
Username = fwcc
Password = fwccpwd
ReadOnly = no
[FWCC Admin]
Driver = <PostgreSQL driver name>
Database = template1
Description = FWCC Administrative Database
Options =
Port = 5432
Servername = <IP address or DNS resolvable host name>
Username = <Root user name defined for PostgreSQL installation>
Password = <Password defined for PostgreSQL root user>
ReadOnly = no
Save odbc_template.ini and close the text editor. Next, the ODBC driver must be installed.
I n s t a l l i n g th e DS N
Open the Terminal application and enter the following:
odbcinst -i -s -l -f <pathname of odbc_template.ini>
Close the Terminal application. Installation of the DSNs necessary for the GTA Reporting Suite 2.0
Database Backend is now complete.

R e f e r e n c e D : Tr o u b l e s h o o t i n g
The following are solutions to frequently asked questions GTA has encountered.
Installation Issues
W h e n i n s t a l l i n g G TA R e p o r t i n g S u i t e 2 . 0 o n t o M i c r o s o f t W i n d o w s , I
r e c e i v e a n e r r o r s t a t i n g I a m m i s s i n g a r e q u i r e d DLL . H o w c a n I f i x
this?
To resolve the issue, download Microsoft’s .NET Framework version 2.0. The installer can be
obtained from http://msdn.microsoft.com/netframework/downloads/updates/default.aspx.
Client Issues
W h y d o I r e c e i v e J a v a e r r o r s w h e n t r y i n g t o l a u n c h t h e G TA
Reporting Suite 2.0 Client?
The GTA Reporting Suite Client requires Java Runtime Environment version 1.5 or greater and Java
Web Start to run. To download the latest version, visit http://java.com/en/download/index.jsp.
W h y d o e s t h e G TA R e p o r t i n g S u i t e 2 . 0 C l i e n t f a i l t o d o w n l o a d
o r c o n n e c t w h e n I ’ m a c c e s s i n g G TA R e p o r t i n g S u i t e 2 . 0 f r o m a n
external host?
If you are receiving an error that states, “Java Web Start Download Error” or “Unable
to Launch GTA Reporting Suite”, then it is likely that the Firewall Control Center or GTA
Reporting Suite is targeting the local host in the *.conf files instead of the server’s DNS entry.
To resolve the issue you will need to update the *.conf files to reflect the server’s DNS name
instead of the local host. For Microsoft Windows installations, *.conf files are stored in the
FWCC-DB and FWCC-Server folders in the installation directory. For Linux installations, *.conf
files are stored in /usr/local/etc.
Note
The default installation directory for Microsoft Windows is C:\Program Files\GTA\FWCC-2.0.1\.

C e r t a i n r e p o r t s d o n o t s e e m t o w o r k w h e n I t r y t o r u n t h e m . W h y ?
The majority of reports listed under Internet Access Management, Email Summary and Virus Summary require
either GBAuth to be enabled or Surf Sentinel or Mail Sentinel Anti-Virus or Anti-Spam subscrip-
tions.
For additional information on available reports and their requirements, please refer to Reference B:
Reports.
M y l i c e n s e i s b e i n g r e p o r t e d a s i n v a l i d b y t h e G TA R e p o r t i n g S u i t e
2.0 Client. Why?
In most cases, a loss of connection to the GTA Licenses Server (als.gta.com) for more than 72
hours will cause the license to become invalid. After reconnection to the Internet the Firewall
Control Center Server should be able to re-check the licenses. Alternatively, you may reboot the
Firewall Control Center Server or restart the Firewall Control Center service on the server.
Your license will also be reported as invalid if you are running an evaluation version of GTA
Reporting Suite 2.0 and your evaluation has expired.
I c o n f i g u r e d a n d a d d e d a f i r e w a l l t o t h e G TA R e p o r t i n g S u i t e 2 . 0
Client but it is greyed out and labeled as “Disabled”. Why?
Verify that the Firewall Control Center service has been enabled and configured. A possible reason
for this is because your licenses have been exceeded. To verify this, check the firewall and GTA
Reporting Suite 2.0 log files.
On the GTA firewall, navigate to Monitor>System>Log Messsages. If your licenses have been exceeded,
the following message will be displayed:
Nov 16 11:28:42 pri=4 msg=”GBC: Disabled by server” type=mgmt src=10.10.1.96
srcport=3892 dst=10.10.1.237 dstport=2033
The GTA Reporting Suite log file will also state the following:
License count exceeded.FIREWALL=”63000488” has been disconnected.
I’ve lost the user ID and/or password to my administrative account.

How can I retrieve them?
If you have lost your administrator’s user ID and/or password you will need to drop or delete the
gbusers table in the database.
Note
Consult your database’s documentation on how to drop or delete a table.
After the table has been dropped or deleted, the Firewall Control Center Server and Database
Backend will need to be restarted. After the Firewall Control Center Server and the Firewall
Control Center Database Backend have successfully restarted the administrator’s user name will
default to Administrator with a password of fwccpwd.

Server Issues
u p o n l a u n c h i n g t h e G tA r e p o r t i n g S u i t e 2 . 0 c l i e n t I g e t a n “ u n a b l e
t o l a u n c h G tA r e p o r t i n g S u i t e ” e r r o r. W h y ?
Check to make sure GTA Reporting Suite 2.0 states that the license is valid, the license count is
correct and that the Database Backend is up and running. Also verify that GTA Reporting Suite
2.0 is targeting the correct host in the *.conf files, which are located under FWCC-DB and FWCC-
Server folders in the installation directory for Microsoft Windows. For Linux installations, *.conf
files are stored in /usr/local/etc.
Note
The default installation directory for Microsoft Windows is C:\Program Files\GTA\FWCC-2.0.1.
W h e n I t r y t o m o v e G tA r e p o r t i n g S u i t e 2 . 0 t o a n e w h o s t , I c a n n o t
activate the service. Why?
GTA Reporting Suite 2.0 licenses allow for one installation at a time. Should you need to move the
server to another host or if the GTA Reporting Suite 2.0 Client or Server shows your serial number
as invalid, it is possible to reset your serial number for re-installation.
To do so, log into the GTA Support Center (https://www.gta.com/support/center/), and click the
View Your Registered Products link. If you have already registered your copy of GTA Reporting Suite 2.0,
the serial number should be displayed in the View Your Registered Products section. If the serial number
is not displayed, your copy of the software needs to be registered.
Clicking on your GTA Reporting Suite 2.0 serial number will display the details of your product. A
link will be available that states License Token: rESEt lIcEnSE toKEn. Click the rESEt lIcEnSE
toKEn link. Resetting the license token will release the license for re-installation.
Figure D.2: Resetting the License Token
You can now reboot the Firewall Control Center Server or restart the Firewall Control Center
service. Alternatively, you may wait up to 30 minutes as the server periodically checks for a new
license. Once the server has successfully connected the License Token will return to rESEt
lIcEnSE toKEn.
My Firewall control center Server cannot activate its license or

f a i l s t o c o n n e c t t o t h e l i c e n s e s s e r v e r. W h y ?
Check to make sure the server can resolve the GTA licenses server (als.gta.com). Also, verify on
your GTA firewall that a security policy is not in place that denies SSL (TCP port 443) access to the
Internet.
GTA Reporting Suite 2.0 User’s Guide Reference D: Troubleshooting 87

My event log states “... entries in Message Queue removing oldest
e n t r y. D a t a i s b e i n g l o s t ! ” . W h y ?
A data loss occurs when the message buffer on the Firewall Control Center Server is full. The data
loss can be resolved by increasing the message buffer. To do so, open the GBCserver.conf file
and add the following on a new line:
MsgQue Per FW=”200”
For Microsoft Windows installations, *.conf files are stored in the FWCC-DB and FWCC-Server
folders in the installation directory. For Linux installations, *.conf files are stored in /usr/local/etc.
Note
The default installation directory for Microsoft Windows is C:\Program Files\GTA\FWCC-2.0.1\.
Additionally, you may wish to adjust the log messages that GTA firewalls are sending to the
88 GTA Reporting Suite 2.0 User’s Guide Reference D: Troubleshooting

Database Backend Issues
What tables in the database are affected by the nightly backup and
purge?
GTA Reporting Suite 2.0 performs a nightly backup and purge, which occurs at midnight, on the
following tables:
• alarm
• alarm_address
• alarm_filter
• alarm_port
• alarmrule
• log
• nat_close
• smtp
• audit
What is the format for the file name used for the nightly backup
and purge?
Backups created by the nightly backup and purge are named in the format of yyyymmdd_
hhmm_<table_name>.xml, where <table_name> is replaced with the name of the table being
purged.
For example, 20060116_0000_alarm.xml.
H o w l o n g i s d a t a s t o r e d i n t h e d a t a b a s e b e f o r e i t i s r e m o v e d b y
the nightly backup and purge? Is this configurable?
By default, data is stored in the database for the following periods of time:
• Log Data: 7 days
• Alarm Data: 30 days
• Audit Data: 30 days
• Report Data: 30 days
To configure the amount of time before data is removed from the database by the nightly backup
and purge, open the “gta_firewall” database. Within the “purge_tables” table is the “period” field.
Integer values within the “period” field correspond the number of days before a record is backed
up and purged from the database.
G TA R e p o r t i n g S u i t e 2 . 0 s t o p p e d l o g g i n g d a t a . W h y ?
If you have an event log that states, “Could not allocate space for object ‘####’ in
database ‘gta_firewall’ because the primary firewall group is full”, on query
of “insert into ... table)name(fields...) values (#,#,#,#)”, then it is likely that
your database is full. You may receive this error message twice, this is expected.
Microsoft SQL Express 2005 databases are limited to 4 GBs of storage. To resolve the issue, you
will need to backup and purge the database. See Purging Records from the Database on how to
purge records.
Additional information can be found at http://msdn.microsoft.com/vstudio/express/sql/.

W h e n I i n s t a l l e d G TA R e p o r t i n g S u i t e 2 . 0 f r o m t h e CD , I a l s o
installed Microsoft SQL Express 2005. What is the instance name?
By default, the Microsoft SQL Express 2005 instance name created when installing GTA Reporting
Suite 2.0 from the CD is GTAFWCC.
I have recently installed MySQL 4.0 but it does not always

correctly start up as a service. Why?
If MySQL 4.0 does not properly start up as a service, you will need to tell it do so.
To install MySQL 4.0 so that it starts as a service on Microsoft Windows:
1. Open the command prompt (Start>Run, type cmd and then OK).
2. At the command prompt, enter C:/mysql/bin/mysqld-max-nt --install to install
MySQL as a service.
3. To verify that MySQL is now running as a service, open the Services utility
(Start>Control Panel>Administrative Tools>Services). If the service has not been started, right click on the
MySQL row and select Start from the menu.
When using Microsoft SQL Server for my Database Backend, I see

“Login failed not trusted SQL connection” in my event log. Why?
Full error message:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Login failed for user
‘(null)’. Reason: Not associated with a trusted SQL Server connection.
If you encounter this message in your event log, it is because your SQL database was set to use a
Microsoft Windows user account for its logins.
To set the SQL database to use its own user accounts, open the Enterprise Manager utility. Right-
click on the database instance and select Properties from the menu. In the Properties window,
select the Security tab. Under the Authentication section select the SQL Server and Windows radio
button.
Why is the database name not displayed on the Server Status page
of the Firewall Control Center Server?
If you are using PostgreSQL to run your Database Backend, the Database Name field on the Server
Status page of the Firewall Control Center Server will be blank. PostgreSQL does not provide this
information via ODBC.

When using MySQL installed on Linux for my Database Backend,
the Firewall Control Center Server connects, then disconnects and
subsequently fails to reconnect. Why?
This can occur when the Firewall Control Center Server is pointing to a MySQL database with an
ODBC Connector using version 3.51.12 of the MySQL driver from MySQL’s website. Possible log
messages that may be created by this error:
Aug 9 15:09:42 dhcp238 GBCD: CODBC_Connection::connect() ::SQLDriverConnect (
DSN=FWCC;UID=fwcc;PWD=fwccpwd;) failed. ERROR(-1) [unixODBC][MySQL][ODBC 3.51
Driver]Can’t initialize character set latin1 (path: /usr/share/mysql/char-
sets/)
Aug 9 15:09:42 dhcp238 GBCDB: Opening database in ProcessDBRequest() failed!
Retry=1
If you encounter these messages in your event log, it is necessary to download and edit the ODBC
connector’s source files (available from http://www.mysql.org/downloads/connector/odbc/). Once
downloaded, navigate to the driver folder and open the dll.c file for editing. Line 118, which states
my_end(0);, needs to be commented out. Save and close the dll.c file. Next, navigate up one
level to the mysql-connector-odbc folder and run the following commands, in order:
1. ./configure - The configure command defines how the code is compiled, linked, and
installed.
2. make - The make command builds the drivers.
3. make install - The make install command installs the drivers. You will need to be
logged in as root to use the make install command.
Once the code has been compiled and installed, it may be necessary to copy the new drivers to
the location where the old drivers are stored. The new drivers, which may be placed in the /usr/
local/lib directory, will need to be copied to the /usr/lib directory.
Caution
When copying drivers, do not overwrite the ibmyodbc3.so, libmyodbc3_r.so or the libmyodbc3S.so
references. Doing so may compromise your installation.

Why do remote connections to a PostgreSQL server fail?
By default, PostgreSQL does not allow remote connections. In order to allow remote connections
in a distributed installation two configuration files must be edited:
pg_hba.conf
postgresql.conf
These files will need to be updated in order to allow remote connections and to start PostgreSQL
on interfaces besides the loopback.
Example: pg_hba.conf, adding a local network:
# TYPE DATABASE USER CIDR-ADDRESS METHOD
#IPv4 local connections
host all all 127.0.0.1/32 md5 # Loopback
host all all 192.168.71.0/24 trust # Local Network
Example: postgresql.conf, adding a line to allow connections to interface:
#listen_addresses = ‘localhost’# what IP interface(s) to listen on;
# defaults to localhost, ‘*’ = any
listen_addresses = ‘*’
After the necessary changes have been made to the .conf files, the PostgreSQL service will need
to be restarted.
Why am I receiving an error message stating the Database Backend

server is down or unreachable?
Example error message:
CODBC_Connection::connect() ::SQLDriverConnect(DSN=FWCC;UID=fwcc;PWD=fwccpwd)
failed. ERROR(-1)
Could not connect to the server;
Could not connect to remote socket.
[Microsoft][ODBC Driver Manager] Driver’s SQLSetConnectAttr failed
This error message can be generated for a variety of reasons:
• The Database Backend server is offline
• The Database Backend service on the server has stopped
• The Database Backend server has not been configured to accept remote connections
• GTA Reporting Suite 2.0 is targetting the incorrect host in the *.conf files
Configuration files are located under FWCC-DB and FWCC-Server folders in the Microsoft
Windows installation directory. For Linux installations, *.conf files are stored in /usr/local/etc.
Note
The default installation directory for Microsoft Windows is C:\Program Files\GTA\FWCC-2.0.1.

Copyright
© 1996-2008, Global Technology Associates, Incorporated (GTA). All rights reserved.
Except as permitted under copyright law, no part of this manual may be reproduced or distributed in any form or by any means without the prior
permission of Global Technology Associates, Incorporated.
Technical Support
GTA includes 30 days “up and running” installation support from the date of purchase. See GTA’s web site for more information. GTA’s direct
customers in the USA should call or email GTA using the telephone and email address below. International customers should contact a local GTA
authorized channel partner.
Tel: +1.407.380.0220 Email: support@gta.com
Disclaimer
Neither GTA, nor its distributors and dealers, make any warranties or representations, either expressed or implied, as to the software and docu-
mentation, including without limitation, the condition of software and implied warranties of its merchantability or fitness for a particular purpose.
GTA shall not be liable for any lost profits or for any direct, indirect, incidental, consequential or other damages suffered by licensee or others
resulting from the use of the program or arising out of any breach of warranty. GTA further reserves the right to make changes to the specifica-
tions of the program and contents of the manual without obligation to notify any person or organization of such changes.
Mention of third-party products is for informational purposes only and constitutes neither an endorsement nor a recommendation for their use.
GTA assumes no responsibility with regard to the performance or use of these products.
Every effort has been made to ensure that the information in this manual is accurate. GTA is not responsible for printing or clerical errors.
Trademarks & Copyrights

GB-OS, Surf Sentinel, Mail Sentinel and GB-Ware are registered trademarks of Global Technology Associates, Incorporated. GB Commander
is a trademark of Global Technology Associates, Incorporated. Global Technology Associates and GTA are service marks of Global Technology
Associates, Incorporated.
Microsoft, Internet Explorer, Microsoft SQL and Windows are either trademarks or registered trademarks of Microsoft Corporation in the United
States and/or other countries.
Adobe and Adobe Acrobat Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or
other countries.
UNIX is a registered trademark of The Open Group.
Linux is a registered trademark of Linus Torvalds.
BIND is a trademark of the Internet Systems Consortium, Incorporated and University of California, Berkeley.
WELF and WebTrends are trademarks of NetIQ.
Sun, Sun Microsystems, Solaris and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other
countries.
Java software may include software licensed from RSA Security, Inc.
Some products contain software licensed from IBM are available at http://oss.software.ibm.com/icu4j/.
Some products include software developed by the OpenSSL Project (http://www.openssl.org/).
Kaspersky Lab and Kaspersky Anti-Virus is licensed from Kaspersky Lab Int. Some products contain technology licensed from Kaspersky Lab Int.
Mailshell and Mailshell Anti-Spam is a trademark of Mailshell Incorporated. Some products contain technology licensed from Mailshell
Incorporated.
All other products are trademarks of their respective companies.
Global Technology Associates, Inc.

3505 Lake Lynda Drive, Suite 109 • Orlando, FL 32817 USA
Tel: +1.407.380.0220 • Fax: +1.407.380.6080 • Web: http://www.gta.com • Email: info@gta.com

GTA Reporting Suite 2 Guide

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

GTA Reporting Suite 2 Guide

Caricato da

Copyright:

Formati disponibili

GTA Reporting Suite

GTA Reporting Suite 2.0 User’s Guide Contents iii

iv GTA Reporting Suite 2.0 User’s Guide Contents

GTA Reporting Suite 2.0 User’s Guide Introduction 1

Firewall Control Center Server

2 GTA Reporting Suite 2.0 User’s Guide Introduction

Bold Italics Emphasis

GTA Reporting Suite 2.0 User’s Guide Introduction 3

4 GTA Reporting Suite 2.0 User’s Guide Installation

Figure 2.1: Configuring the Firewall

About Firewall Pre-shared Secrets

GTA Reporting Suite 2.0 User’s Guide Installation 5

Select your desired installation type and click Next.

Figure 2.2 Selecting the Installation Type

6 GTA Reporting Suite 2.0 User’s Guide Installation

Figure 2.3: Entering the Serial Number and Verification Code

Figure 2.4: Selecting the Installation Path

Figure 2.5: Entering the Service Owner

GTA Reporting Suite 2.0 User’s Guide Installation 7

Figure 2.6: Creating the DSN

Figure 2.7: Entering the Instance Name

8 GTA Reporting Suite 2.0 User’s Guide Installation

Figure 2.8: Entering the Database Administrator

Figure 2.9 : Entering Server Information

Figure 2.10: Entering Email Server Information

GTA Reporting Suite 2.0 User’s Guide Installation 9

Figure 2.11: Entering the Serial Number and Verification Code

Figure 2.12: Selecting the Installation Path

Figure 2.13: Entering the Service Owner

10 GTA Reporting Suite 2.0 User’s Guide Installation

Figure 2.14: Entering the Database Server Host Information

Figure 2.15: Entering Server Information

Figure 2.16: Entering Email Server Information

GTA Reporting Suite 2.0 User’s Guide Installation 11

Figure 2.17: Selecting the Installation Path

Figure 2.18: Entering the Service Owner

12 GTA Reporting Suite 2.0 User’s Guide Installation

Figure 2.19: Creating the DSN

Figure 2.20: Entering the Instance Name

GTA Reporting Suite 2.0 User’s Guide Installation 13

Figure 2.21: Entering the Database Administrator

D o c u me ntatio n On ly In stallat ion

14 GTA Reporting Suite 2.0 User’s Guide Installation

GTA Reporting Suite 2.0 User’s Guide Installation 15

Running the Installer

Figure 2.21: Accepting the License Agreement

16 GTA Reporting Suite 2.0 User’s Guide Installation

Figure 2.25: Configuring GBCserver.conf

GTA Reporting Suite 2.0 User’s Guide Installation 17

Running the Installer

Figure 2.26: Accepting the License Agreement

18 GTA Reporting Suite 2.0 User’s Guide Installation

Figure 2.27: Configuring GBCdb.conf

Starting The Service

GTA Reporting Suite 2.0 User’s Guide Installation 19

Figure 2.21: Reinstalling GTA Reporting Suite 2.0

20 GTA Reporting Suite 2.0 User’s Guide Installation

Connecting to the Firewall Control Center

Figure 3.1: Firewall Control Center Server Page

Figure 3.3: Firewall List

Figure 3.4: Adding Groups and Firewalls

Adding Firewall Groups

Removing Firewall Groups