SteelCentral™ Flow Gateway Software

SteelCentral™ Flow Gateway Software
Installation Guide
Virtual Edition for VMware ESXi 5.0, 5.1 and 5.5
Version 10.8
January 2015
© 2015 Riverbed Technology. All rights reserved.
Riverbed®, SteelApp™, SteelCentral™, SteelFusion™, SteelHead™, SteelScript™, SteelStore™, Steelhead®, Cloud Steelhead®, Virtual
Steelhead®, Granite™, Interceptor®, Stingray™, Whitewater®, WWOS™, RiOS®, Think Fast®, AirPcap®, BlockStream™, FlyScript™,
SkipWare®, TrafficScript®, TurboCap®, WinPcap®, Mazu®, OPNET®, and Cascade® are all trademarks or registered trademarks of
Riverbed Technology, Inc. (Riverbed) in the United States and other countries. Riverbed and any Riverbed product or service name or logo
used herein are trademarks of Riverbed. All other trademarks used herein belong to their respective owners. The trademarks and logos
displayed herein cannot be used without the prior written consent of Riverbed or their respective owners.
F5, the F5 logo, iControl, iRules and BIG-IP are registered trademarks or trademarks of F5 Networks, Inc. in the U.S. and certain other
countries. Linux is a trademark of Linus Torvalds in the United States and in other countries. VMware, ESX, ESXi are trademarks or registered
trademarks of VMware, Incorporated in the United States and in other countries.
Portions of SteelCentral™ products contain copyrighted information of third parties. Title thereto is retained, and all rights therein are reserved,
by the respective copyright owner. PostgreSQL is (1) Copyright © 1996-2009 The PostgreSQL Development Group, and (2) Copyright © 19941996 the Regents of the University of California; PHP is Copyright © 1999-2009 The PHP Group; gnuplot is Copyright © 1986-1993, 1998,
2004 Thomas Williams, Colin Kelley; ChartDirector is Copyright © 2007 Advanced Software Engineering; Net-SNMP is (1) Copyright ©
1989, 1991, 1992 Carnegie Mellon University, Derivative Work 1996, 1998-2000 Copyright © 1996, 1998-2000 The Regents of The
University of California, (2) Copyright © 2001-2003 Network Associates Technology, Inc., (3) Copyright © 2001-2003 Cambridge Broadband
Ltd., (4) Copyright © 2003 Sun Microsystems, Inc., (5) Copyright © 2003-2008 Sparta, Inc. and (6) Copyright © 2004 Cisco, Inc. and
Information Network Center of Beijing University of Posts and Telecommunications, (7) Copyright © Fabasoft R&D Software; Apache is
Copyright © 1999-2005 by The Apache Software Foundation; Tom Sawyer Layout is Copyright © 1992 - 2007 Tom Sawyer Software; Click
is (1) Copyright © 1999-2007 Massachusetts Institute of Technology, (2) Copyright © 2000-2007 Riverbed Technology, Inc., (3) Copyright
© 2001-2007 International Computer Science Institute, and (4) Copyright © 2004-2007 Regents of the University of California; OpenSSL is
(1) Copyright © 1998-2005 The OpenSSL Project and (2) Copyright © 1995-1998 Eric Young (eay@cryptsoft.com); Netdisco is (1) Copyright
© 2003, 2004 Max Baker and (2) Copyright © 2002, 2003 The Regents of The University of California; SNMP::Info is (1) Copyright © 20032008 Max Baker and (2) Copyright © 2002, 2003 The Regents of The University of California; mm is (1) Copyright © 1999-2006 Ralf S.
Engelschall and (2) Copyright © 1999-2006 The OSSP Project; ares is Copyright © 1998 Massachusetts Institute of Technology; libpq++ is
(1) Copyright © 1996-2004 The PostgreSQL Global Development Group, and (2) Copyright © 1994 the Regents of the University of
California; Yahoo is Copyright © 2006 Yahoo! Inc.; pd4ml is Copyright © 2004-2008 zefer.org; Rapid7 is Copyright © 2001-2008 Rapid7
LLC; CmdTool2 is Copyright © 2008 Intel Corporation; QLogic is Copyright © 2003-2006 QLogic Corporation; Tarari is Copyright © 2008
LSI Corporation; Crypt_CHAP is Copyright © 2002-2003, Michael Bretterklieber; Auth_SASL is Copyright © 2002-2003 Richard Heyes;
Net_SMTP is Copyright © 1997-2003 The PHP Group; XML_RPC is (1) Copyright © 1999-2001 Edd Dumbill, (2) Copyright © 2001-2006
The PHP Group; Crypt_HMAC is Copyright © 1997-2005 The PHP Group; Net_Socket is Copyright © 1997-2003 The PHP Group;
PEAR::Mail is Copyright © 1997-2003 The PHP Group; libradius is Copyright © 1998 Juniper Networks. This software is based in part on the
work of the Independent JPEG Group the work of the FreeType team.
This documentation is furnished "AS IS" and is subject to change without notice and should not be construed as a commitment by Riverbed
Technology. This documentation may not be copied, modified or distributed without the express authorization of Riverbed Technology and
may be used only in connection with Riverbed products and services. Use, duplication, reproduction, release, modification, disclosure or
transfer of this documentation is restricted in accordance with the Federal Acquisition Regulations as applied to civilian agencies and the
Defense Federal Acquisition Regulation Supplement as applied to military agencies. This documentation qualifies as "commercial computer
software documentation" and any use by the government shall be governed solely by these terms. All other use is prohibited. Riverbed
Technology assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation.
Individual license agreements can be viewed at the following location: https://<appliance_name>/license.php
This manual is for informational purposes only. Addresses shown in screen captures were generated by simulation software and are for
illustrative purposes only. They are not intended to represent any real traffic or any registered IP or MAC addresses.
Riverbed Technology
680 Folsom Street
San Francisco, CA 94107
Phone: 415.247.8800
Fax: 415.247.8801
Web: http://www.riverbed.com
Part Number
712-00133-05
Contents
Chapter 1 - Introduction.............................................................................................................................1
Additional Resources........................................................................................................................................1
Contacting Riverbed .........................................................................................................................................2
Chapter 2 - Preparing for installation .......................................................................................................3
Required software and hardware ......................................................................................................................3
Data sources......................................................................................................................................................4
Network access .................................................................................................................................................4
Configuration information ...............................................................................................................................5
Chapter 3 - Deploying the Flow Gateway .................................................................................................9
Uploading the Flow Gateway OVA package to the ESXi host ........................................................................9
Chapter 4 - Configuring the Flow Gateway ............................................................................................ 15
Accessing the Flow Gateway..........................................................................................................................15
Initial setup .....................................................................................................................................................17
Chapter 5 - Activating the licenses......................................................................................................... 19
Obtaining license keys from the licensing portal ...........................................................................................19
Entering license keys in the Flow Gateway....................................................................................................21
Chapter 6 - Verifying the installation ...................................................................................................... 23
SteelCentral™ Flow Gateway Software Installation Guide
iii
Contents
iv
SteelCentral™ Flow Gateway Software Installation Guide
CHAPTER 1
Introduction
The virtual edition of the Riverbed® SteelCentral™ Flow Gateway is a virtualized implementation of the Flow
Gateway appliance. This document describes how to install the virtual edition on a VMware ESXi host.
The installation process includes:

Chapter 2, “Preparing for installation”

Chapter 3, “Deploying the Flow Gateway”

Chapter 4, “Configuring the Flow Gateway”

Chapter 5, “Activating the licenses”

Chapter 6, “Verifying the installation”
When the installation tasks are completed, the Flow Gateway is ready to configure operationally. Operational
configuration is described in the on line help system.
Additional Resources
The primary source of product information is the on line help system. Additional information is available from the
Riverbed Support site at https://support.riverbed.com. This includes:

Release Notes - posted on the Software page for your product. Choose your product from the Software menu.

Users Guides - posted on the Documentation page for your product. Choose your product from the
Documentation menu.

Tech Notes - linked to from the Documentation page for your product. Choose your product from the
Documentation menu.

Knowledge Base - a database of known issues and how-to documents. You can browse titles or search for key
words and strings. Choose “Search the Knowledge Base” from the Knowledge Base menu.
SteelCentral™ Flow Gateway Software Installation Guide
1
Introduction
Contacting Riverbed
Contacting Riverbed
Options for contacting Riverbed include:

Internet - Find out about Riverbed products at http://www.riverbed.com.

Support - If you have problems installing, using, or replacing Riverbed products, contact Riverbed Technical
Support or your channel partner who provides support. To contact Riverbed Technical Support, please open a
trouble ticket at https://support.riverbed.com or call 1-888-RVBD-TAC (1-888-782-3822) in the United States
and Canada or +1 415 247 7381 outside the United States.

Professional Services - Riverbed has a staff of engineers who can help you with installation, provisioning,
network redesign, project management, custom designs, consolidation project design, and custom-coded
solutions. To contact Riverbed Professional Services, go to http://www.riverbed.com or email
proserve@riverbed.com.

Documentation - Riverbed continually strives to improve the quality and usability of its documentation. We
appreciate any suggestions you may have about our on line documentation or printed materials. Send
documentation comments to techpubs@riverbed.com.
2
SteelCentral™ Flow Gateway Software Installation Guide
CHAPTER 2
Preparing for installation
When you purchase the Flow Gateway, you receive a license activation token in email. Ensure that you have this token.
Also ensure that:

The required hardware and software are available.

Ports are open to allow the Flow Gateway to receive information from other SteelCentral products and to access
required network services.
Required software and hardware
Hardware requirements depend on the licensed flow limits. For an ESXi host that is running only the Flow Gateway,
the recommended computing resources are as follows.
Product Code
License Type
Flow Limit
Minimum
Recommended
SCFG-VE-F1
MSPECSCFGVFLOW1
15k FPM
2 CPU
2GB RAM
2 CPU
4GB RAM
SCFG-VE-F2
MSPECSCFGVFLOW2
30k FPM
2 CPU
2GB RAM
2 CPU
4GB RAM
SCFG-VE-F3
MSPECSCFGVFLOW3
60k FPM
2 CPU
2GB RAM
2 CPU
4GB RAM
SCFG-VE-F4
MSPECSCFGVFLOW4
90k FPM
2 CPU
2GB RAM
2 CPU
4GB RAM
SCFG-VE-F5
MSPECSCFGVFLOW5
200k FPM
2 CPU
4GB RAM
4 CPU
8GB RAM
SCFG-VE-F6
MSPECSCFGVFLOW6
400k FPM
2 CPU
4GB RAM
4 CPU
8GB RAM
SCFG-VE-F7
MSPECSCFGVFLOW7
600k FPM
4 CPU
8GB RAM
4 CPU
16GB RAM
SCFG-VE-F7
MSPECSCFGVFLOW8
800k FPM
4 CPU
8GB RAM
4 CPU
16GB RAM
SteelCentral™ Flow Gateway Software Installation Guide
3
Preparing for installation
Data sources
Product Code
License Type
Flow Limit
Minimum
Recommended
SCFG-VE-F7
MSPECSCFGVFLOW9
1M FPM
4 CPU
16GB RAM
8 CPU
24GB RAM
SCFG-VE-F7
MSPECSCFGVFLOW10
2M FPM
4 CPU
24GB RAM
8 CPU
32GB RAM
The ESXi host must provide the following for the Flow Gateway:

VMware ESXi 5.0, 5.1 or 5.5

Flow Gateway virtual edition OVA package

VMware vSphere Client

ESXi server hardware with at least:
–
Four Virtual CPUs
–
2 GB of RAM
–
50 GB of storage space for system disk
–
2 GB of swap space on the system disk
–
Two NICs
–
AUX interface support for dual-homed mode
It is recommended that the primary virtual disk be “thick provisioned” to ensure the disk space will be available to the
virtual machine. However, primary virtual disk can be “thin provisioned” if there is enough free space on the datastore
to support the size of the disk when it becomes full. If the datastore runs out of disk space when using “thin
provisioned” virtual disks, the virtual machine may become unstable and require re-installation.
Data sources
The Flow Gateway obtains traffic information from NetFlow, IPFIX, Packeteer FDR or sFlow sources, or by
SteelFlow Net or CascadeFlow from a compatible SteelHead. Enable the SNMP ifIndex persistence feature of the
NetFlow source devices to ensure consistency of interface reporting.
There are two approaches to setting up data sources:

Set up the available data sources and point them to the IP address of the Flow Gateway before you install it.

Install the Flow Gateway up to the point of verification, then go install or configure the data sources, and then
return to the Flow Gateway to complete the installation verification.
It is preferable to configure all the data sources that are available at the time you install the Flow Gateway. However,
Flow Gateway operation can be confirmed with just one data source.
Network access
The Flow Gateway uses the management network to communicate with other SteelCentral products and to access
network services.
4
SteelCentral™ Flow Gateway Software Installation Guide
Configuration information
Preparing for installation
Communication between SteelCentral products
If you lock down your network on a port-by-port basis, ensure that the following ports are open between SteelCentral
products:

TCP/22 – (ssh) This is needed for the Flow Gateway to receive upgrade packages from a NetProfiler.

TCP/8443 – Exchange of encryption certificates between the Flow Gateway and a NetProfiler.

TCP/41017 – Encrypted communication between the Flow Gateway and a NetProfiler.

UDP/123 – (ntp) Synchronization of time between the Flow Gateway and a NetProfiler.
Access to and from network access services

TCP/22 – (ssh) This is needed for secure shell access to product software components.

TCP/443 – (https) Secure web-based management interface.
Configuration information
When you configure the Flow Gateway, you will be asked to provide configuration information. Information that is
required to complete the installation is listed in the table that follows with an asterisk (*). Items not marked with an
asterisk are optional during installation and can be specified afterwards on the Flow Gateway Configuration > General
Settings page if necessary.
It may be useful to write the configuration values in the blank column of the checklist below so that you can refer to
them during the configuration step or afterward.
Flow Gateway host name:*
Flow Gateway IP address:*
Netmask:*
Default gateway:*
DNS name resolution for hosts (enable or disable):
Primary DNS server IP address:
Secondary DNS server IP address:
DNS search domain:
Primary port settings:
(10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate)
Switch port settings:
The settings of the switch port or hub that the Flow Gateway
primary port connects to. (Auto-negotiate is recommended.)
Aux interface IP address
Aux interface netmask
Aux interface switch port settings
Time Zone:
SteelCentral™ Flow Gateway Software Installation Guide
5
Preparing for installation
Configuration information
Flow encryption certificate (default or new certificate):
For faster installation, use the default encryption certificate
shipped with the Flow Gateway and then generate a new
certificate later.
SNMP information:
Flow Gateway is set by default to use SNMP Version 1 and to
allow MIB browsing. If you are configuring SNMP at this
time, obtain the necessary V1 or V3 information.
Data Sources - Use NetFlow
Specify the port number on which the Flow Gateway will
receive the data. Applies only if the Flow Gateway is
receiving NetFlow data (versions 1, 5, 7 or 9), IPFIX,
CascadeFlow, or cFlow data. Do not send more than one type
of flow data to the same port.
Data Sources - Use sFlow
Specify the port number on which the Flow Gateway will
receive the data. Applies only if the Flow Gateway is
receiving sFlow data (versions 2, 4 or 5). Do not send more
than one type of flow data to the same port.
Data Sources - Use Packeteer
Specify the port number on which the Flow Gateway will
receive the data. Applies only if the Flow Gateway is
receiving Packeteer Flow Detail Records (versions 1 or 2). Do
not send more than one type of flow data to the same port.
SNMP information:
The Flow Gateway is set by default to use SNMP Version 1
and to allow MIB browsing. If you are configuring SNMP at
this time, obtain the necessary V1 or V3 information.
First NetProfiler data input address.
The address of the NetProfiler to which the Flow Gateway
will send traffic data. This is the IP address of the
management interface (Primary port) of an NetExpress or
Standard NetProfiler or the address of the first Analysis
Module of an Enterprise NetProfiler.
NetProfiler IP Address:
Flow sources:
If data sent to this NetProfiler is to be limited to only data
received from certain flow sources, then specify those
sources.
Second NetProfiler data input address.
If the Flow Gateway will be sending traffic data to more than
one NetProfiler, this is the IP address of the second
NetProfiler. It is the management interface (Primary port) of
an NetExpress or Standard NetProfiler or the address of the
Analysis Module of an Enterprise NetProfiler.
NetProfiler IP Address:
Flow sources:
If flow forwarding to this NetProfiler is to be limited to only
data received from certain flow sources, then specify those
sources
6
Data Forward - Destination 1
IP address and port number of the first destination to which
the Flow Gateway is to forward flow data, the type of data
(e.g., NetFlow) to be forwarded, and whether or not the source
address of the forwarded packets should be overwritten with
the source address from which they were received.
IP address:
If flow forwarding to this destination is to be limited to data
received from only certain flow sources, then specify those
sources.
Overwrite source address? Yes/No:
Port:
Type:
Source:
SteelCentral™ Flow Gateway Software Installation Guide
Configuration information
Preparing for installation
Data Forward - Destination 2
IP address and port number of the second destination to which
the Flow Gateway is to forward flow data, the type of data
(e.g., NetFlow) to be forwarded, and whether or not the source
address of the forwarded packets should be overwritten with
the source address from which they were received.
IP address:
If flow forwarding to this destination is to be limited to data
received from only certain flow sources, then specify those
sources.
Overwrite source address? Yes/No:
Port:
Type:
Source:
Password to use for your initial Gateway login:*
The default password admin.
New password to enter when prompted to change the initial
Flow Gateway password:*
Applies only to systems not previously configured.
SteelCentral™ Flow Gateway Software Installation Guide
7
Preparing for installation
8
Configuration information
SteelCentral™ Flow Gateway Software Installation Guide
CHAPTER 3
Deploying the Flow Gateway
Deploying the Flow Gateway on an ESXi host involves:

Uploading the Flow Gateway archive (OVA) package to the ESXi host.

Deploying the open virtual format (OVF) template.
Uploading the Flow Gateway OVA package to the ESXi host
Open the VMware vSphere client to get an access to your existing ESXi host. The vSphere client can be downloaded
by pointing your web browser to the IP Address of your ESXi host. For example https://10.32.146.21. Install the Flow
Gateway software on the ESXi host as follows:
1. Using the VMware vSphere client, log in to the ESXi host.
2. In the navigation tree, select the ESXi host on which to deploy the Flow Gateway.
SteelCentral™ Flow Gateway Software Installation Guide
9
Deploying the Flow Gateway
Uploading the Flow Gateway OVA package to the ESXi host
3. Choose Deploy OVF Template from the File menu (File > Deploy OVF Template).
This opens the Deploy OVF Template window.
4. On the Source page, browse to the location of the Flow Gateway OVA file. Alternatively, enter the full path to the
file. Click Next to open the OVF Template Details section.
10
SteelCentral™ Flow Gateway Software Installation Guide
Uploading the Flow Gateway OVA package to the ESXi host
Deploying the Flow Gateway
5. On the OVF Template Details page, confirm that the correct file is selected and click Next.
6. On the Name and Location page, enter a name for the Flow Gateway and click Next.
SteelCentral™ Flow Gateway Software Installation Guide
11
Deploying the Flow Gateway
Uploading the Flow Gateway OVA package to the ESXi host
7. On the Datastore page, select the server drive where you will store the Flow Gateway files and click Next. (The
Datasatore screen is displayed only if you have external storage, such as NAS.).
8. On the Disk Format page, select the disk provisioning format and then click Next.
The Disk Format page for ESXi has three format options.
12
SteelCentral™ Flow Gateway Software Installation Guide
Uploading the Flow Gateway OVA package to the ESXi host
Deploying the Flow Gateway
It is recommended that virtual disks are “thick provisioned” to ensure the disk space will be available to the
virtual machine. However, virtual disks may be “thin provisioned” as long as there is enough free space on the
Datastore to support the size of the disk when it becomes full. If the datastore runs out of disk space when using
“thin provisioned” virtual disks, the virtual machine may become unstable and require reinstallation.
If the “Lazy zero” and “Eager zero” options are available, select “Lazy zero.” Do not use “Eager zero.”
9. On the Network Mapping page, map the source networks (ports) of the Flow Gateway to destination networks (port
groups) on the server and click Next.
SteelCentral™ Flow Gateway Software Installation Guide
13
Deploying the Flow Gateway
Uploading the Flow Gateway OVA package to the ESXi host
10. On the Ready to Complete summary page, click Finish to start the deployment.
When the deployment has completed, you can see the resulting network structure on the Configuration page
Networking section. In the example configuration shown below, the Flow Gateway has been added to the server as
Flow Gateway virtual edition. The Network 1 port is mapped to the Management Network port group and the Network
2 port is mapped to the VM network.
14
SteelCentral™ Flow Gateway Software Installation Guide
CHAPTER 4
Configuring the Flow Gateway
Configuring the Flow Gateway includes:

Using the vSphere client to access the Flow Gateway console port to set up the Flow Gateway to be accessible
over the network.

Using the Flow Gateway web user interface to complete further configuration tasks if necessary before activating
the licenses.
Accessing the Flow Gateway
The first step in configuring the Flow Gateway is to set up its IP address, subnet mask, and default gateway so that you
can access the web user interface. You perform this configuration using the Flow Gateway console port, as follows.
1. On the vSphere client’s list of virtual machines, select the icon for the Flow Gateway.
SteelCentral™ Flow Gateway Software Installation Guide
15
Configuring the Flow Gateway
Accessing the Flow Gateway
2. On the Getting Started tab, click Power on the virtual machine.
3. On the tool bar of the vSphere client, click the console launch button to open a console session on the Flow
Gateway.
4. Log in to the Flow Gateway console using the default user name and password:
Login: admin
Password: admin
5. Follow the prompts to enter the IP address, subnet mask and default gateway for the Flow Gateway.
6. Check to ensure that the settings have been entered correctly and then enter “yes” to reboot the Flow Gateway. The
console login session is terminated when the Flow Gateway reboots.
Do not use the console admin account except for this setup procedure. If it is necessary to log in to the console or
command line interface later, use the mazu account.
16
SteelCentral™ Flow Gateway Software Installation Guide
Initial setup
Configuring the Flow Gateway
Initial setup
The first time you log in to the Flow Gateway web user interface, the software displays a setup page. Parts of this page
are prepopulated with the IP address, subnet mask, and default gateway that you specified using the console port in the
previous step. This may be all you need to complete the installation. However, you can specify the rest of the initial
configuration information at this time.
1. On the management network, point your web browser to the IP address you specified in the configuration wizard
using the console port.
https://<Flow_Gateway_IP_address>
2. Log in to the Flow Gateway web user interface. The default credentials are:

User name: admin

Password: admin
The first time you log in to the Flow Gateway user interface, it displays the Setup page.
3. On the Setup page, ensure that all the required fields (marked with an asterisk) are filled in.
4. Fill in the additional information, as necessary:

Name Resolution - whether to use DNS resolution for hosts reported by the Flow Gateway and, if so, the
addresses and search domains for the DNS servers.

AUX Interface - If you are using the AUX interface, enter the IP address, netmask and connection settings.
SteelCentral™ Flow Gateway Software Installation Guide
17
Configuring the Flow Gateway
Initial setup

Static Routes - If there are multiple subnets on the Aux interface network, or if you need to use a gateway router
other than the default gateway, it may be necessary to define static routes.

Time Configuration - Time zone.

Data Sources - The Flow Gateway can be configured to receive traffic flow information from devices using
NetFlow (versions 1, 5, 7 and 9), SteelFlow Net, CascadeFlow, IPFIX, sFlow (versions 2, 4 and 5), and Packeteer
(versions 1 and 2). You can specify one or more ports in a comma-separated list for each type of flow data, up to
a combined total of 50 ports.
You can also exclude data sources. Flow Gateway ignores data sent to it from addresses listed in the Excluded
Sources box. For example, it drops NetFlow data sent to it from a router whose address is listed in the Excluded
Sources box.
When Flow Gateway is configured to use the Aux and Management interfaces on separate networks, use the
Allow on interface option to control which interface is to receive traffic flow data.

SNMP MIB Configuration - Flow Gateway is set by default to use SNMP Version 1 and to allow MIB browsing. If you
are configuring SNMP at this time, obtain the necessary V1 or V3 information.
5. After you have filled in all necessary fields, click Configure Now at the bottom of the page to apply your changes.
Your browser session will be closed while the configuration changes are made. You can then log back in to activate
your licenses.
18
SteelCentral™ Flow Gateway Software Installation Guide
CHAPTER 5
Activating the licenses
When you purchase a Flow Gateway, your purchase confirmation email includes a license request token. The Flow
Gateway uses this token to generate a license activation code, which you use to obtain license keys from the Riverbed
licensing portal.
When you enter the license activation code on the Riverbed licensing portal, the portal generates a license key for each
license you have purchased. You copy these keys and enter them on the Flow Gateway licensing page to activate the
licenses features.
Obtaining license keys from the licensing portal
To get the license keys for the features you have purchased,
1. Log in to the Flow Gateway web user interface.
2. Navigate to the Configuration > Licenses page.
SteelCentral™ Flow Gateway Software Installation Guide
19
Activating the licenses
Obtaining license keys from the licensing portal
3. Paste or enter your license activation token in the License Request section and click Request key. The Flow
Gateway generates a license activation code and displays it in a popup window.
4. Copy the activation code.
5. Go to the Riverbed licensing portal at https://licensing.riverbed.com.
6. Paste or enter your activation code into the Enter Unique Product Identifier field and click Next.
7. Follow the instructions in the licensing wizard. The licensing portal will activate all the licenses that you purchased
on the order for which you received the token.
8. When the process is complete, copy the license keys from the list. These must be entered in the Flow Gateway.
20
SteelCentral™ Flow Gateway Software Installation Guide
Entering license keys in the Flow Gateway
Activating the licenses
Entering license keys in the Flow Gateway
Enter your license keys in the Flow Gateway to activate the licenses you have purchased.
1. Log in to the Flow Gateway web user interface.
2. Navigate to the Configuration > Licenses page and click Add license(s) in the Licenses section. This opens a
popup window for entering the license keys.
3. Enter the license keys as a comma-separated list and click OK. The Flow Gateway activates the licenses and
displays them in a list. Your web user interface session may be terminated when the new licenses are activated. If
it is, log back in and navigate to the Configuration > Licenses page.
SteelCentral™ Flow Gateway Software Installation Guide
21
Activating the licenses
Entering license keys in the Flow Gateway
4. Review the list of licenses if necessary.
After the licenses have been installed, you can verify the installation by checking to see if the Flow Gateway is
monitoring traffic.
22
SteelCentral™ Flow Gateway Software Installation Guide
CHAPTER 6
Verifying the installation
Verify that the Flow Gateway has been successfully installed and configured by logging in and checking the Overview
page. The Overview page identifies all traffic information sources that are currently sending data to the Flow Gateway.
Also, it identifies destinations to which the Flow Gateway forwards traffic information.
If flow sources are currently configured to send data to the Flow Gateway, they should be displayed on the Overview
page. If NetProfilers are receiving data from the Flow Gateway, they should also be displayed on the Overview page.
SteelCentral™ Flow Gateway Software Installation Guide
23
Verifying the installation
You can also navigate to the System > Information page and ensure that the System Status and Storage Status
indicators are green.
This completes the installation process. The Flow Gateway can now be turned over to those who are responsible for
setting up user accounts and operational parameters. Refer to the on line help system for further configuration
procedures.
24
SteelCentral™ Flow Gateway Software Installation Guide
SteelCentral™ Flow Gateway Software Installation Guide
25
Riverbed Technology
680 Folsom Street
San Francisco, CA 94107
Phone: 415.247.8800
Fax: 415.247.8801
Web: http://www.riverbed.com
Part Number
712-00133-05
Open as PDF
Similar pages