Flow Gateway Ig Azure 10 24
Flow Gateway Ig Azure 10 24
Version 10.24
January 2023
© 2023 Riverbed Technology, Inc. All rights reserved.
Riverbed®, SteelConnect™, SteelCentral™, SteelHead™, and SteelFusion™ 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.
This document is furnished "AS IS" and is subject to change without notice and should not be construed as a commitment by
Riverbed. Riverbed does not provide any warranties for any information contained herein and specifically disclaims any liability
for damages, including without limitation direct, indirect, consequential, and special damages in connection with this
document. This document may not be copied, modified or distributed without the express authorization of Riverbed and may
be used only in connection with Riverbed products and services. Use, duplication, reproduction, release, modification,
disclosure or transfer of this document 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 document 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 assumes no responsibility or liability for any errors or inaccuracies that may appear herein.
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 Part Number
www.riverbed.com 712-00133-19
1 - Introduction .......................................................................................................................................................4
Additional Resources ..................................................................................................................................... 5
Contacting Riverbed ...................................................................................................................................... 5
This document describes the deployment and configuration of SteelCentral™ Flow Gateway Virtual
Edition as a cloud-based virtual appliance in Microsoft Azure.
Additional Resources
The primary source of product information is the online 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.
Contacting Riverbed
Options for contacting Riverbed include:
When you purchase the Flow Gateway, you receive an email with a license activation token. Verify that
you have this token before you deploy the product.
You must also verify that the required hardware and software are available, and that network ports are
open to allow the Flow Gateway to receive information from other SteelCentral products and to access
required network services.
Data sources
Flow Gateway receives traffic information from NetFlow, IPFIX, sFlow. NetShark, and AppResponse 11,
or compatible Packeteer FDR sources. It also receives SteelFlow Net information from SteelHead
(formerly called CascadeFlow). This includes application identification, QoS configuration and flow data.
SteelFlow Net is a standards-compliant variant of NetFlow v9 that uses a custom Riverbed template to
send standard NetFlow data as well as more specialized metrics.
For Flow Gateway to receive flow data from NetFlow-enabled devices, enable the SNMP ifIndex
persistence feature of the NetFlow source to ensure consistency of interface reporting.
Additionally, Riverbed SteelCentral Agent and Amazon Web Services Virtual Private Cloud networks can
be configured to send cloud flow data to Flow Gateway.
• 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. Some basic requirements are listed in the sections that follow, for
detailed information on which ports and protocols must be open, refer to the SteelCentral Network
Performance Management Deployment Guide.
Configuration information
When you configure the Flow Gateway, you will be prompted to provide configuration information. The
available configuration settings are listed in the table below.
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.
Time Zone:
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.
– Specify a username and password—Specify ‘mazu’ as the username and provide a password for
the account.
7. Under Disk Options, select a disk type for Flow Gateway appliance’s operating system—Premium SSD
compatibility is recommended, but not required.
8. Under Data Disks, create and attach a disk or (attach an existing disk) for buffered flow data.
The Flow Gateway software is preconfigured to use the main volume where the Flow Gateway is
installed.
Important: Do not modify the preconfigured operating system disk during this process.
We recommend that you add an additional virtual hard disk to store buffered flow data. If you do
not already have a storage disk, select Create and Attach a new disk.
– In the Create a new disk page, specify these settings: disk type, display name, size in
gigabytes(GB), source type.
The second drive, for buffered flow data, should be between 500GB and 2TB in size.
– Click OK. The virtual disk(s) with your settings is allocated. The Create a new disk page closes
and you are returned to the wizard’s Disk tab. The newly allocated disk is listed under Data Disks.
– Select Read/Write from the Host Caching drop-down menu corresponding to the newly
allocated disk.
If you already have a data store disk, select Attach an existing disk.
– A row is added to the Data Disks table.
– Select a disk from the Name drop-down menu.
– Select Read/Write from the Host Caching drop-down menu corresponding to the newly added
disk.
10. Click Next : Networking > to advance to the wizard’s Networking tab.
11. Select the network and subnet where you want to deploy the Flow Gateway from the Virtual network
and Subnet drop-down menus. You should configure settings according to your infrastructure setup.
For example, the subnet that you assign should be one from which the Flow Gateway will be able to
communicate with the NetProfiler and any appliances from which it receives flow data.
If you have not already configured a virtual network and a subnet, click Create new to display the
Create new network page. Enter an address space for the new virtual network, create subnets, and
then click OK. See the Microsoft Azure help for assistance.
12. Optionally select a public IP address from the Public IP drop-down menu. A public IP enables you to
communicate with the virtual appliance from outside the virtual network.
If you want to use a public IP but none exist, click Create new to display the Create public IP address
page. Enter a display name for the new IP address, specify SKU and assignment, and then click OK.
See the Microsoft Azure help for assistance.
13. NIC network security group is Advanced. NIC network security group settings are preconfigured.
14. Select a network security group from the Configure network security group drop-down menu.
If no security groups exist, click Create new to display the Create network security group page,
specify Inbound rules and Outbound rules, and then click OK. See the Microsoft Azure help for
assistance.
17. Click Next : Management > to advance to the wizard's Management tab.
18. Optionally configure the settings under Monitoring, Identity, and Auto-Shutdown to your liking.
19. Click Next : Advanced > to advance to the wizard's Advanced tab.
20. Click Next : Tags > to advance to the wizard's Tags tab.
22. Click Next : Review + create > to advance to the wizard's Review + create tab.
After you deploy the Flow Gateway Virtual Edition on your VM, you can configure the Flow Gateway
environment. This chapter describes how you enable network access to the product and complete
additional configuration before you activate the product licenses.
The appliance configures itself during the firstboot process which can take more than an hour
depending on system size. During this time, basic status messages are provided via the web user
interface and command line interface. Once firstboot completes, the appliance reboots and finishes
configuration so it is ready to use. You will know it is complete when the login screen appears in the web
user interface.
The web user interface will be available for login when the Flow Gateway is ready. 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. Complete the initial configuration
as described below.
1. On the management network, use a web browser to navigate to the IP address of the new VM.
https://<Flow_Gateway_IP_address>
2. Log in to the Flow Gateway web user interface. Use the default user name and password “admin”
The first time you log in to the Flow Gateway user interface, it displays the Setup page.
– AUX Interface - If you intend to use the AUX interface, enter the IP address, netmask and
connection settings.
– 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, you can define static routes.
– Time Configuration - Specify the time zone.
– Data Sources - You can configure the Flow Gateway 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 you configure Flow Gateway to use the Aux and Management interfaces on separate
networks, select 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, V2C, or V3 information.
5. In the Change password page, change the password for the admin user.
This process updates the password used for the “admin” user in the WebUI, as well as the mazu/
root/admin/dhcp system user accounts. The system account passwords can each be changed later
using the Administration > Appliance Security > Security Compliance page.
This step also disables shell access to the device. You can enable shell access by selecting the Login
enabled checkbox on the Administration > Appliance Security > Security Compliance page.
Your browser session closes while the configuration changes are made. You can then log back in to
activate your licenses.
When you purchase the Flow Gateway, your purchase confirmation email includes a license request
token. You use this token to generate a license request key, that 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. Copy these keys and enter them on the Flow Gateway
licensing page to activate the licenses features.
3. Paste or enter your license request token in the License request token field and click Submit.
The Flow Gateway generates a license activation code and displays it in a popup window.
2. Navigate to the Administration > Licenses page and click Add license(s) in the Licenses section.
The licenses window opens.
The Flow Gateway activates the licenses and displays them in a list. If your web user interface
session is terminated when the new licenses are activated, log back in and navigate to the
Administration > Licenses page.
• Verify the installation by checking to see if the Flow Gateway is monitoring traffic
• Go to the Administration > NetProfiler Export page and configure the Flow Gateway to send traffic
to the NetProfiler. For details, see the NetProfiler Export topic in the online help.
Flow Gateway can receive flow data from software running in the cloud and send the flow data to
NetProfiler for analysis and reporting. The sources of cloud flow data include:
https://support.riverbed.com/content/support/software/steelcentral-npm/appresponse-ar11.html
SteelCentral Agent
Flow Gateway can receive flow data from SteelCentral Agent to provide visibility into the cloud. This
requires deploying the agent and using the SteelCentral AppInternals product to configure it. Refer to
“Deploying the Agent as an NPM Data Source” in the AppInternals user documentation for instructions
on how to deploy and configure the agent.
https://doc.steelcentral.net/help/wwhelp/wwhimpl/js/html/
wwhelp.htm?context=config_reference&topic=agentnpmdatasource