Академический Документы
Профессиональный Документы
Культура Документы
Configuration Guide
Version 5.0
April 2017
© 2017 Riverbed Technology, Inc. All rights reserved.
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.
Akamai® and the Akamai wave logo are registered trademarks of Akamai Technologies, Inc. SureRoute is a service mark of
Akamai. Apple and Mac are registered trademarks of Apple, Incorporated in the United States and in other countries. Cisco
is a registered trademark of Cisco Systems, Inc. and its affiliates in the United States and in other countries. EMC, Symmetrix,
and SRDF are registered trademarks of EMC Corporation and its affiliates in the United States and in other countries. IBM,
iSeries, and AS/400 are registered trademarks of IBM Corporation and its affiliates in the United States and in other
countries. Juniper Networks and Junos are registered trademarks of Juniper Networks, Incorporated in the United States and
other countries. Linux is a trademark of Linus Torvalds in the United States and in other countries. Microsoft, Windows, Vista,
Outlook, and Internet Explorer are trademarks or registered trademarks of Microsoft Corporation in the United States and in
other countries. Oracle and JInitiator are trademarks or registered trademarks of Oracle Corporation in the United States and
in other countries. UNIX is a registered trademark in the United States and in other countries, exclusively licensed through X/
Open Company, Ltd. VMware, ESX, ESXi are trademarks or registered trademarks of VMware, Inc. in the United States and in
other countries.
This product includes Windows Azure Linux Agent developed by the Microsoft Corporation (http://www.microsoft.com/).
Copyright 2016 Microsoft Corporation.
This product includes software developed by the University of California, Berkeley (and its contributors), EMC, and Comtech
AHA Corporation. This product is derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm.
The SteelHead Mobile Controller (virtual edition) includes VMware Tools. Portions Copyright © 1998-2016 VMware, Inc. All
Rights Reserved.
NetApp Manageability Software Development Kit (NM SDK), including any third-party software available for review with such
SDK which can be found at http://communities.netapp.com/docs/DOC-1152, and are included in a NOTICES file included
within the downloaded files.
For a list of open source software (including libraries) used in the development of this software along with associated
copyright and license agreements, see the Riverbed Support site at https//support.riverbed.com.
This documentation is furnished “AS IS” and is subject to change without notice and should not be construed as a
commitment by Riverbed. This documentation 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 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 assumes no responsibility or liability for any
errors or inaccuracies that may appear in this documentation.
Riverbed Technology
680 Folsom Street
San Francisco, CA 94107 Part Number
www.riverbed.com 712-00272-07
Contents
Welcome .............................................................................................................................................. 5
About this guide ...................................................................................................................... 5
Audience ........................................................................................................................... 5
Document conventions...................................................................................................... 6
Safety guidelines..................................................................................................................... 6
Documentation and release notes ........................................................................................... 6
Contacting Riverbed ................................................................................................................ 7
3 - Installing and Configuring the SteelFusion Edge Appliance (iSCSI/Block Mode) .......................... 27
Deploying the SteelFusion Edge appliance ............................................................................ 27
Checking your inventory ........................................................................................................ 28
Preparing your site for installation ........................................................................................ 29
Site requirements ........................................................................................................... 29
SteelFusion Edge ports ................................................................................................... 30
Network interface cards and expansion slots.................................................................. 32
Avoiding duplex mismatch............................................................................................... 33
Completing the configuration checklist .......................................................................... 34
Powering on the appliance .................................................................................................... 34
Configuring SteelFusion Edge appliances.............................................................................. 35
Connecting the SteelFusion Edge to your network........................................................... 35
Connecting virtual machines to the Edge appliance ........................................................ 37
Running the Configuration Wizard ................................................................................... 37
Verifying you are connected to the appliance .................................................................. 42
Connecting to the Management Console ......................................................................... 44
Verifying WAN optimization ............................................................................................. 45
Checking for speed and duplex errors.............................................................................. 45
Next steps ............................................................................................................................. 46
4 - Installing and Configuring the SteelFusion Edge Appliance (NFS/File Mode) ............................... 47
Deploying the SteelFusion Edge appliance ............................................................................ 47
Checking your inventory ........................................................................................................ 48
Preparing your site for installation ........................................................................................ 49
Site requirements ........................................................................................................... 49
SteelFusion Edge ports ................................................................................................... 50
Network interface cards and expansion slots.................................................................. 52
Avoiding duplex mismatch............................................................................................... 53
Completing the configuration checklist .......................................................................... 54
Powering on the appliance .................................................................................................... 54
Configuring SteelFusion Edge appliances.............................................................................. 55
Connecting the SteelFusion Edge to your network........................................................... 56
Connecting hypervisor storage network to the Edge VIP .................................................. 57
Running the Configuration Wizard ................................................................................... 58
Verifying you are connected to the appliance .................................................................. 62
Connecting to the Management Console ......................................................................... 64
Verifying WAN optimization ............................................................................................. 65
Checking for speed and duplex errors.............................................................................. 65
Next steps ............................................................................................................................. 66
Audience
This guide is written for storage and network administrators familiar with administering and managing
WANs using common network protocols such as TCP, CIFS, HTTP, FTP, and NFS.
This guide includes information relevant to these products and product features:
Riverbed SteelFusion Edge (Edge appliance)
Riverbed SteelFusion Core (Core)
Riverbed Optimization System (RiOS)
Riverbed SteelHead CX (SteelHead)
Riverbed SteelHead EX (EX)
SteelCentral Controller for SteelHead (SCC)
Riverbed command-line interface (CLI)
This guide is intended to be used with these documents:
SteelFusion Edge Hardware and Maintenance Guide
SteelFusion Edge Management Console User’s Guide
SteelFusion Design Guide
SteelFusion Command-Line Interface Reference Manual
SteelFusion Core Installation and Configuration Guide
SteelFusion Core Management Console User’s Guide
Document conventions
This guide uses the following standard set of typographical conventions.
Convention Meaning
italics Within text, new terms and emphasized words appear in italic typeface.
boldface Within text, CLI commands, CLI parameters, and REST API properties appear in bold typeface.
<> Values that you specify appear in angle brackets: interface <ip-address>
[] Optional keywords or variables appear in brackets: ntp peer <ip-address> [version <number>]
{} Elements that are part of a required choice appear in braces: {<interface-name> | ascii
<string> | hex <string>}
| The pipe symbol separates alternative, mutually exclusive elements of a choice. The pipe
symbol is used in conjunction with braces or brackets; the braces or brackets group the
choices and identify them as required or optional: {delete <filename> | upload <filename>}
Safety guidelines
Follow the safety precautions outlined in the Safety and Compliance Guide when installing and setting
up your equipment.
Caution: Failure to follow these safety guidelines can result in injury or damage to the equipment. Mishandling of
the equipment voids all warranties. Read and follow safety guidelines and installation instructions carefully.
Many countries require the safety information to be presented in their national languages. If this
requirement applies to your country, consult the Safety and Compliance Guide. Before you install,
operate, or service the Riverbed products, you must be familiar with the safety information. Refer to the
Safety and Compliance Guide if you do not clearly understand the safety information provided in the
product documentation.
Examine the release notes before you begin the installation and configuration process.
Contacting Riverbed
This section describes how to contact departments within Riverbed.
Technical support - Problems installing, using, or replacing Riverbed products? Contact Riverbed
Support or your channel partner who provides support. To contact Riverbed Support, open a
trouble ticket by calling 1-888-RVBD-TAC (1-888-782-3822) in the United States and Canada or +1
415-247-7381 outside the United States. You can also go to https://support.riverbed.com.
Professional services - Need help with planning a migration or implementing a custom design
solution? Contact Riverbed Professional Services. Email proserve@riverbed.com or go to http://
www.riverbed.com/services/index.html.
Documentation - Have suggestions about Riverbed’s online documentation or printed materials?
Send comments to techpubs@riverbed.com.
Introducing SteelFusion
SteelFusion is a converged infrastructure solution, encompassing all branch services such as server,
storage, networking, and WAN optimization. It is a dual-ended system that comprises two logical
components: SteelFusion Edge and SteelFusion Core.
Core is a physical or virtual appliance in the data center that mounts all storage (LUNs in iSCSI mode or
exports in NFS mode) that need to be made available to applications and servers at a remote location
from the back-end storage array. Edge provides a virtualized environment that hosts the branch
application servers. Core appliances communicate across the WAN with the Edge appliances at the
branch.
SteelFusion delivers local user performance while enabling data centralization, instant recovery, and
lower total operating costs. Unlike traditional converged infrastructures, SteelFusion enables stateless
branch services. You can access applications that run locally in the branch while the primary data is
centralized in the data center, allowing applications to run in a stateless mode.
You can extend a data center storage array to a remote location, even over a low-bandwidth link.
SteelFusion provides the following functionality:
Innovative storage optimization ensures that you can centrally manage data storage while keeping
that data available to business operations in the branch, even in the event of a WAN outage.
A local authoritative cache ensures LAN-speed reads and fast cold writes at the branch.
Integration with Microsoft Volume Shadow Copy Service enables consistent point-in-time data
snapshots and seamless integration with backup applications.
Integration with the snapshot capabilities of the storage array enables you to configure
application-consistent snapshots through the SteelFusion Core Management Console.
iSCSI/block mode only - Integration with industry-standard Challenge-Handshake Authentication
Protocol (CHAP) authenticates users and hosts.
A secure vault protects sensitive information using AES 256-bit encryption.
Solid-state disks (SSDs) that guarantee data durability and performance.
An active-active high-availability (HA) deployment option for Core ensures the availability of
storage for remote sites.
Customizable reports provide visibility to key utilization, performance, and diagnostic information.
SteelFusion Edge - Edge refers to the branch component of the SteelFusion solution. The Edge
hosts two distinct functions, or nodes:
– WAN optimization
– Hypervisor platform with VMware vSphere
When deployed in an iSCSI configuration, the Edge presents itself to application servers in the
branch as an iSCSI storage portal. From the portal, the application server uses iSCSI to mount the
iSCSI LUNs that are projected across the WAN from the data center. Edge can also host local LUNs
for use as temporary storage that are not projected from the data center: for example, temporary or
local copies of software repositories.
When deployed in an NFS configuration, Edge presents NFS version 3 storage exports projected
from the data center as local exports to applications and servers at the local branch.
LUN (iSCSI mode only) - A unique identifier associated with individual storage devices or
collections of storage devices used with SCSI, iSCSI, or Fibre Channel interfaces.
Export (NFS/file mode only) - A unique identifier associated with file systems or directories
located on a backend storage array that are accessible to the Core. NFS exports are mounted on
the Core and then mapped to the Edge at the branch. When the Core is running in NFS/file mode, it
uses the NFS protocol to talk to the storage array and presents exports to the branches. The terms
NFS mode and File mode can be used interchangeably.
Branch server - The branch-side servers access data from the SteelFusion system instead of a
local storage device. This server can also run as a Virtual Services Platform (VSP) VM on the local
Edge.
Blockstore - A persistent and authoritative local cache of storage on the Edge that caches the
writes on LUNs/exports presented by the Edge. Blockstore also stores cached portions of the
LUNs/exports to quickly serve read requests.
Figure 1-1. Typical SteelFusion deployment
For detailed information about SteelFusion and how it works, see the SteelFusion Edge Management
Console User’s Guide and the SteelFusion Design Guide.
These terms will help you understand SteelFusion and its features.
Virtualization - All software and hardware concerning the installation, deployment, and
management of the hypervisor and virtual machines (VMs). Virtualization encompasses both RiOS
and hypervisor hardware nodes.
Note: Virtualization is not available in Virtual Edge.
Hypervisor - VMware virtualization software running on bare-metal hardware that creates and
runs VMs.
Note: Hypervisor functionality is not available in Virtual Edge.
Virtual Services Platform (VSP) - Software that runs as a part of the RiOS networking and
optimization software. VSP manages, communicates with, and reports on the hypervisor.
RiOS node - Hardware node that manages and controls WAN optimization, direct attached storage,
and VSP.
Hypervisor node - Hardware node where hypervisor-based hardware resources and software
virtualization are deployed.
Interconnects - Internal TCP network used to communicate to and from RiOS and the hypervisor
nodes.
The physical node design provides true hardware resource separation and isolation. These two
computing nodes are connected through Gigabit Ethernet interconnects that allow both nodes to
communicate for management, networking, and storage data. Each node has its own resources. For
example each node has its own sensors for temperature, voltage, and dual in-line memory modules
(DIMMs).
RiOS node
The RiOS node incorporates SteelHead RiOS 9.5.0a features to provide WAN optimization. All features
available with RiOS 9.5.0a are available on the Edge appliance. You manage the storage and networking
components using the SteelFusion Management Console, and you utilize VMware vSphere Client or
vCenter to interact with the hosted VMs.
The RiOS node also includes the VSP management software for virtualization.
iSCSI/block mode - the RiOS node provides BlockStream iSCSI storage for the hypervisor
datastores. You configure the space allotted to the BlockStream iSCSI storage using the
SteelFusion Edge Management Console Hypervisor Installer.
NFS/file mode - the RiOS node provides NFS storage for the hypervisor datastores. You configure
the space allotted to the NFS storage using the SteelFusion Edge Management Console Hypervisor
Installer.
For detailed information about the Hypervisor Installer, see the SteelFusion Edge Management Console
User’s Guide.
Hypervisor node
The hypervisor node is a bare-metal virtualization platform that enables you to run multiple VMs on the
Edge appliance. With the hypervisor node, you can consolidate multiple basic services in the branch
such as Active Directory (AD), Domain Name Service (DNS), print server, and file server. You install and
run VMs directly from the hypervisor node of the Edge appliance.
The hypervisor uses the ESXi 5.5 Patch 9 software as the virtualization platform. The hypervisor is
included in the Edge appliance and does not require a separate download. After you install the Edge
appliance, you set up the hypervisor using the Edge Management Console Installer.
You set up and configure VMs through the VMware vSphere Client or a licensed vCenter. You must install
the VMware vSphere Hypervisor Client, which enables monitoring and management of a single instance
of the ESX or ESXi server. You can download the vSphere applications from the VMware website, or you
can download the vSphere Client from the hypervisor host.
The hypervisor node enables you to connect to the hypervisor serial console using the RiOS CLI
command hypervisor console. You can also perform debugging by connecting via Secure Shell (SSH) to
the hypervisor baseboard management controller (BMC) internal IP address. For detailed information,
see the SteelFusion Command-Line Interface Reference Manual and the SteelFusion Edge Hardware
and Maintenance Guide.
Networking interfaces
The Edge hardware platform includes:
Management/Base interfaces - The primary (PRI) and auxiliary (AUX) interfaces provide
management network ports for the RiOS node, and can also be used for connecting Edge to Core. In
NFS/file mode, these interfaces can also be used for an Edge VIP interface or even high availability.
You can view these interfaces in the Networking > Networking: Base Interfaces page.
Bypass interfaces - A preinstalled network interface card (NIC) (LANX_Y, WANX_Y) provides
SteelHead bypass ports on the RiOS node and is used for optimization. You can view these
interfaces in the Networking > Networking: In-Path Interfaces page.
Data/Storage interfaces - The storage ports (eth0_0, eth0_1) on the RiOS node provide external
storage or high availability connections, and in NFS/file mode they can be used for an Edge VIP
interface. You can view these interfaces in the Networking > Networking: Data Interfaces page.
Hypervisor data interfaces - For the hypervisor node, any of the four data ports labeled gbe0_0,
gbe0_1, gbe0_2, and gbe0_3 can be used for virtualization depending on the hypervisor
configuration. You configure these ports during the initial configuration using the Edge
Management Console Hypervisor Installer and manage them using VMware vSphere Client or
vCenter.
SteelFusion Edge Management Console Any computer that supports a web browser with a
color image display.
The SteelFusion Edge Management Console has been
tested with Mozilla Firefox Extended Support Release
version 38.0, Google Chrome, and Microsoft Internet
Explorer 11.0.
JavaScript and cookies must be enabled in your web
browser.
BlockStream, SteelFusion Core Management Console Version 5.0 (Cores in NFS/file mode)
Version 4.5 or later (Cores in iSCSI/block mode)
Note: Software versions for Core and Edge cannot be
more than two major releases apart. For example, 4.0
and 4.2 are compatible, but 4.0 and 4.3 are not
compatible.
SCC compatibility
To manage SteelFusion Edge 5.0 appliances, you need to use SCC 9.5.1. Earlier versions of the SCC do
not support 5.0 SteelFusion Edges. For details about SCC compatibility across versions, see the
SteelCentral Controller for SteelHead Installation Guide.
Note: As a result of updating the version of SSH, older releases of SCC cannot connect to newer software on
managed appliances. If you plan to upgrade your Edge appliances to 5.0, first upgrade the SCC to 9.2 (or later) to
avoid disconnections. See Knowledge Base article S27759 for complete details.
SteelFusion Edge model Blockstore (GB) Usable storage (GB) Maximum pinnable
storage (GB)
This value refers to the This value refers to the This value refers to the
space after RAID space available to store maximum space that can
configuration for the LUNs after accounting for be reserved by pinned
entire blockstore. the metadata. The LUNs. This is lower than
metadata uses usable storage to ensure
approximately 8% of the that a minimum amount
size of the blockstore. of space is reserved for
writes.
Note: The Edge Management Console Installer displays the available physical storage using base 2 (that is, 1024
bytes = 1 KB) rather than base 10 (that is, 1000 bytes = 1 KB). The base 10 value is used in this table and the
specification sheet for the appliance. Please be aware of the slight difference between these values when you are
calculating the available space for your deployment. For example, when 2.6 TB is displayed in the Edge Installer it
represents 2.9 TB of available space.
There are two types of licenses that you can purchase to enable vCenter support:
vSphere license - This license is installed into the vSphere instance of the Edge appliance. This
license controls the infrastructure capabilities of the hypervisor, for example: vMotion, evMotion,
distributed resource scheduler (DRS), high availability (HA), fault tolerance (FT). It does not restrict
how many appliances can be connected to vCenter. You can purchase this license and add it to your
ESXi instance in vCenter.
vCenter Server license - This license is installed onto the vCenter server. There are two levels for
this license: foundation and standard. The foundation license provides management tools for up to
three vSphere hosts. The standard license provides large scale management of VMware vSphere
deployments for up to 1000 vSphere hosts. If you want to manage more than three ESXi hosts, you
must purchase the vCenter Server license.
We recommend purchasing a vCenter Server license as it enables monitoring and management of
multiple ESX, ESXi, and GSX servers. In addition, the vCenter Server license provides infrastructure
services such as vMotion, evMotion, DRS, HA, and FT.
Firewall requirements
We recommend that you deploy the Edge appliance behind your firewall. The ports 7800 and 7810 must
be open.
Gigabit Ethernet over Copper 1000BASE-T (All copper IEEE 802.3 - 2008
interfaces are autosensing for speed and duplex.)
Gigabit Ethernet over Fiber 1000BASE-SX (LC connector) IEEE 802.3 - 2008
Gigabit Ethernet over Fiber 10GBASE-LR Single Mode IEEE 802.3 - 2008
The Edge appliance ports support these connection types and speeds.
Port Speed
The Edge appliance supports VLAN Tagging (IEEE 802.3 - 2008). It does not support the Inter-Switch
Link (ISL) protocol.
The Edge appliance autonegotiates speed and duplex mode for all data rates and supports full duplex
mode and flow control (IEEE 802.3 – 2008).
1. Download the software image from the Riverbed Support site to a location such as your desktop.
Optionally, you can download a delta image directly from the Riverbed Support site to the
SteelHead. The delta downloaded image includes only the incremental changes. The smaller file
size means a faster download and less load on the network.
2. Log in to the Edge Management Console using the Administrator account (admin).
3. Choose Administration > Maintenance: Software Upgrade and click Add Image to expand the page.
Control Description
From Riverbed Support Site Select this option and select the target release number from the Version
drop-down list. The system uploads the new image from the Riverbed
Support site immediately after you click Add Image.
If you receive an “entitlement error” warning, you may not have the correct
credentials for the Riverbed Support site. Contact Riverbed Support at
https://support.riverbed.com.
From Local File Select this option and specify the path, or click Browse to go to the local file
directory.
If you specify a file to upload in the Local File text box, the image is uploaded
immediately; however, the image is installed and the system is rebooted at
the time you specify.
Filename Specify a new name for the added image. The default name is
hyp_image.img.iso.
Add Image Click to add the new image to the Hypervisor Images list.
After the reboot, the Home page, Software Upgrade, and Help pages of the Management Console
display the software version upgrade.
Hosts that were previously added to the domain are no longer joined to the domain. When
upgrading from vSphere 5.5 to vSphere 6.0 for the first time, the Active Directory configuration is
not retained. After the upgrade, rejoin the hosts to the vCenter Server domain.
There is no upgrade path from SteelHead EX appliance to the Edge appliance as they are different
products that run on different hardware platforms.
If your SteelFusion deployment previously consisted of a BlockStream-enabled SteelHead EX
appliance and a SteelFusion Core appliance, and if your data is backed by a SteelFusion Core, you can
migrate your data to the SteelFusion Edge appliance.
To migrate the data, you unmap the LUN from the SteelHead EX appliance and rejoin that LUN to the
new Edge appliance.
If you want to downgrade to a previous version of the SteelFusion Edge software, you must downgrade
to a version of the software that has previously run on your machine.
When you downgrade the software, RiOS reverts the ESXi version to the version supported in the
installation image. If you upgraded the ESXi using vCenter (separate from the EX installation), the
system cannot restore the state and ESXi starts with the initial configuration.
RiOS appliances cannot use an encrypted RiOS data store with an earlier RiOS version, unless the
release is an update (9.0.x). For example, an encrypted RiOS data store created in 9.0.1 would work with
9.0.3, but not with 9.1.
Before downgrading to an earlier software version, you must select none as the encryption type, clear
the RiOS data store, and restart the service in the Management Console Data Store page. After you clear
the RiOS data store, the data is removed from persistent storage and cannot be recovered. For detailed
information, see the SteelFusion Edge Management Console User’s Guide.
This chapter describes the Riverbed licensing methods and how to manage Riverbed licenses. It
includes these sections:
“Riverbed licensing methods” on page 23
“Automatic licensing” on page 24
“Manual licensing using the Riverbed Licensing Portal” on page 25
Automatic licensing
Automatic licensing allows the appliance, once connected to the network, to automatically contact the
Riverbed Licensing Portal to retrieve and install license keys onto the appliance. Automatic licensing
simplifies inventory management and provides an automated mechanism of fetching licenses for
Riverbed products without having to manually activate individual appliances and licenses.
If you are behind a firewall, you can retrieve licenses at the Riverbed Licensing Portal using the email
option or by downloading an XML file to the appliance. For detailed information, see “Retrieving
licenses using the Riverbed Licensing Portal” on page 25.
Automatic licensing also works over a web proxy. For details on setting up a web proxy, see the
SteelHead Management Console User’s Guide.
Note: If automatic licensing fails, an error message is displayed in the Management Console. Go to the Riverbed
Licensing Portal and follow the instructions for retrieving your licenses.
1. In the Management Console, choose Configure > Maintenance: Licenses to display the Licenses
page.
3. Click Next.
4. Provide the contact information for the license, including your name and email.
5. Click Submit to display license information for all the products purchased with the serial number
you specified.
7. Optionally, if you are behind a firewall, type the email address in the Email address text box and click
Email Keys to have the license keys emailed to you.
Note: Click New Search to look for additional license records.
1. Connect to the Management Console. For details, see the SteelFusion Edge Management Console
User’s Guide.
4. Copy and paste the license key provided by the Riverbed Licensing Portal into the text box. Separate
multiple license keys with a space, Tab, or Enter.
<license-key> is the license key you retrieved from the Riverbed Licensing Portal.
Caution: Read and follow the safety guidelines described in the Safety and Compliance Guide. Failure to follow
these safety guidelines can result in damage to the equipment.
For detailed information about installing the appliance to a rack, see the SteelFusion Edge Hardware
and Maintenance Guide.
For detailed information about your deployment options and best practices for deploying Edge
appliances, see the SteelFusion Design Guide.
Figure 3-1. SteelFusion Edge in-path deployment
You can also deploy the Edge appliance for high availability (HA) where Edge and Core appliances are
deployed as pairs so that if either peer fails, the surviving Edge or Core appliances can take over. We
strongly recommend that you deploy Edge appliances as pairs in an HA cluster configuration. For
detailed information about HA, see the SteelFusion Edge Management Console User’s Guide and the
SteelFusion Design Guide.
Figure 3-2. SteelFusion Edge high availability deployment
You must always connect the Edge appliance using either the cable in the accessories box or
another cable that is approved for use by the IEC in the country in which the appliance is
connected.
You cannot connect the Edge appliance directly to multiphase outlets. You must use a rack power
distribution unit (PDU) or power strip that provides the appropriate three-prong outlet (hot/
neutral/ground). For details, see the Knowledge Base solution number S13425.
One Phillips screwdriver
Rails
One mounting kit
Documentation kit
If any items are damaged or missing, notify Riverbed Support at https://support.riverbed.com for
replacement or repair.
Site requirements
Before you install the Edge appliance, make sure that your site meets these requirements:
It is a standard electronic environment where the ambient temperature does not exceed 104ºF
(40ºC) and the relative humidity does not exceed 80% (noncondensing). For detailed information,
see the SteelFusion Edge Hardware and Maintenance Guide.
Ethernet connections are available within the standard Ethernet limit.
There is available space on a two-post or four-post 19-inch rack. For details about installing the
Edge to a rack, see the Rack Installation Guide or the printed instructions that were shipped with
the appliance.
A clean power source is available, dedicated to computer devices and other electronic equipment.
The rack is a standard 19-inch Telco-type mounting rack.
Before you begin, consult the SteelFusion Edge Hardware and Maintenance Guide for detailed
information about how to install your model to a rack.
Note: We recommend that you use a four-post mounting rack for 2U appliances.
Note: If your rack requires special mounting screws, contact your rack manufacturer.
Port Description
PRI The primary port connects the Edge appliance to a LAN switch. This interface enables
(Primary) you to connect to the Edge Management Console and the SteelFusion Edge CLI.
This interface can also be used to connect the SteelFusion Core through the RiOS
node, in-path interface.
The primary and auxiliary ports cannot share the same network subnet.
LAN 1_0 (1U) This port connects the LAN port of the Edge appliance to the LAN switch using a
LAN 0_0 (2U) straight-through cable.
The Edge appliance uses one or more in-path interfaces to provide Ethernet network
connectivity for optimized traffic. Each in-path interface comprises two physical
ports: the LAN port and the WAN port. Use the LAN port to connect the Edge appliance
to the internal network of the branch office.
If the Edge appliance is deployed between two switches, both the LAN and WAN ports
must be connected with straight-through cables.
WAN 1_0 (1U) This port connects the WAN port of the Edge appliance to the WAN router using a
WAN 0_0 (2U) crossover cable.
The WAN port is the second of two ports that compose the in-path interface. The WAN
port is used to connect the Edge appliance toward WAN-facing devices such as a
router, firewall, or other equipment located at the WAN boundary.
If you require additional in-path interfaces or require 10GigE or Fiber connectivity, you
can install a bypass NIC in the RiOS node expansion slot.
eth0_0, eth0_1 These ports provide additional iSCSI interfaces for storage traffic to external servers
when used by the RiOS node.
The ports are connected to a LAN switch using a straight-through cable.
These ports can also provide multipath I/O (MPIO) redundancy or SteelFusion Edge
high availability (HA). In an HA deployment, use these ports for BlockStream heartbeat
and synchronization between SteelFusion Edge HA peers. For detailed information
about HA deployments, see the SteelFusion Design Guide.
If you require additional iSCSI connectivity in an HA deployment, install a nonbypass
NIC in the RiOS node expansion slot.
Port Description
RIOS COM A RiOS serial RJ45 communication port that manages the RiOS node. Serial settings:
9600 bps, 8 data bit, 1 stop bit, no parity.
Connects the serial cable to a terminal device. You establish a serial connection to a
terminal emulation program for console access to the configuration wizard and the
Edge CLI.
HYP COM A hypervisor serial RJ45 communication port used to manage the hypervisor node.
Serial settings: 9600 bps, 8 data bit, 1 stop bit, no parity.
VGA Optional Hypervisor VGA connector. This port is useful for BIOS, POST, and PXE
debugging.
Figure 3-3 and Figure 3-4 show the locations of the ports on the rear of the 1U and 2U appliances.
Figure 3-3. 1U back panel
Figure 3-5 shows typical branch office connections for the Edge appliance.
Figure 3-5. Typical SteelFusion Edge port connections 1U appliance
This table summarizes the NIC deployment options for the Edge appliance.
For detailed information about installing additional NICs, see the SteelFusion Edge Hardware and
Maintenance Guide and the SteelFusion Design Guide.
You can connect to a device when you choose autonegotiation, but you cannot connect to that
same device when you manually set the speed or duplex.
Slow performance across the network.
Netmask
DNS IP address
Administrator password
In-path netmask
In-path gateway
Caution: In European electrical environments, you must ground (earth) the green/yellow tab on the power cord or
risk electrical shock.
1. If your appliance has a master power switch, ensure that it is in the off position.
Device Cable
Edge appliance to a switch Straight-through (for example, primary and LAN ports on the appliance to the
LAN switch)
Edge appliance to a router Crossover (for example, WAN port on the appliance to the WAN router)
Device Cable
Edge appliance to a host Crossover (for example, LAN and WAN ports on the Edge appliance bypass
cards act like host interfaces during normal operation)
For detailed information about cabling best practices, see the SteelFusion Design Guide.
1. Plug the straight-through cable into the primary port of the appliance and the LAN switch. The
primary port can be any port on your LAN switch configured to connect to a host.
Figure 3-7. Connecting the primary port to the LAN switch
2. Identify the straight-through cable that connects your LAN switch to your WAN router. Unplug the
end connected to the WAN router.
Figure 3-8. Disconnecting the WAN router
3. Plug the straight-through cable that you disconnected from the WAN router into the LAN port of the
appliance.
Figure 3-9. Connecting the LAN switch to the LAN port
4. Using the provided crossover cable, plug the cable into the WAN port of the appliance and the WAN
router.
Figure 3-10. Connecting the WAN port to the WAN router
Note: If you have additional four-port bypass cards, repeat Step 1 through Step 4. For detailed information about
installing additional bypass cards, see the Network and Storage Card Installation Guide and the SteelFusion Edge
Hardware and Maintenance Guide.
1. Plug the straight-through cable into one of the hypervisor ports: gbe0_0, gbe0_1, gbe0_2, or
gbe0_3.
2. Plug the straight-through cable into any switch that is connected to the hypervisor node.
After you complete the configuration process for the Edge appliance, connect to the Management
Console to configure your hypervisor using the Hypervisor Installer. You can access the Hypervisor
Installer from the Management Console Dashboard or by choosing Virtualization > Installer: Installer.
The hypervisor must be installed before you can host VMs.
Note: Before you launch the Hypervisor Installer, if you are using a SteelFusion Core for storage, you should
configure and connect it before continuing with the installer. A SteelFusion Core allows you to access remote
storage at your data center and make that storage available to your hypervisor. For details, see the SteelFusion Core
Management Console User’s Guide.
1. Plug the serial cable into the RiOS COM port and a terminal.
Figure 3-11. Connecting to the SteelFusion Edge
2. Start your terminal emulation program, such as Tera Term Pro. The terminal device must have these
settings:
Baud rate: 9600 bps
Data bits: 8
Parity: none
Stop bits: 1
vt100 emulation
No flow control
If you are using the Edge appliance with a terminal server, the terminal server must use hardware
flow control for the port connected to the Edge appliance.
We recommend that you connect the console port to a device that logs output to help identify
problems with the system.
3. Log in as administrator user (admin) and enter the default password (password). For example:
login as: admin
Sent username "admin"
password: password
The configuration wizard automatically starts after you have entered the login and default
password. After you have established a connection, you configure the Edge appliance using the
configuration wizard.
4. If you have a SteelCentral Controller for SteelHead (SCC) appliance installed in your network to
manage multiple Edge appliances, you can use it to automatically configure them:
If you answer yes, you are prompted for the SCC hostname or IP address. The hostname or IP
address is used to contact the SCC. The default value is riverbedcmc. If you enter no, the wizard
continues.
Note: If you mistakenly answer yes, to return to the wizard from the CLI, enter the configuration jump-start
command from configuration mode. For detailed information, see “To restart the configuration wizard” on page 41.
5. To start the configuration wizard, type yes at the system prompt and press Enter.
Do you want to use the configuration wizard for initial configuration? yes
Note: Press ? for help; press Ctrl+B to go back to the previous step.
6. Complete the configuration wizard steps on the branch office Edge appliance as described in this
table.
Step 1: Host name? Enter the hostname for the Edge hostname? amnesiac
appliance.
Step 2: Use DHCP on the You are given the option to enable Use DHCP? no
primary interface? the DHCP to automatically assign an
IP address to the primary interface
for the Edge appliance.
We recommend that you do not set
DHCP.
The default value is no.
Step 3: Primary IP address? Enter the IP address for the Edge Primary IP address? 10.10.10.6
appliance.
Step 5: Default gateway? Enter the default gateway for the Default gateway? 10.0.0.1
Edge appliance.
Step 6: Primary DNS server? Enter the primary DNS server IP Primary DNS server? 10.0.0.2
address.
Step 7: Domain name? Enter the domain name for the Domain name? example.com
network where the Edge appliance is
to reside.
If you set a domain name, you can
enter hostnames in the system
without the domain name.
Step 8: Admin password? We strongly recommend that you Admin password? xxxyyy
change the default administrator
password at this time. The password
must be a minimum of six
characters.
The default administrator password
is password.
Step 9: SMTP server? Enter the name of the SMTP server. SMTP server? natoma
External DNS and external access
for SMTP traffic is required for email
notification of events and failures to
function.
Step 10: Notification email Enter a valid email address to which Notification email address?
example@xample.com
address? notification of events and failures
are to be sent.
Step 11: Set the primary Enter the speed on the primary Set the primary interface speed?
[auto] auto
interface speed? interface (that is, the Edge
appliance). Make sure that this value
matches the setting on your router or
switch.
The default value is auto.
Step 12: Set the primary Enter the duplex mode on the Set the primary interface
duplex? [auto] auto
interface duplex? primary interface. Make sure that
this value matches the setting on
your router or switch. The default
value is auto.
Step 13: Would you like to Enter yes at the system prompt to Would you like to activate the
in-path configuration? yes
activate the in-path configure in-path support. An in-
configuration? path configuration is a configuration
in which the Edge appliance is in the
direct path of the client and server.
Step 14: In-Path IP address? Enter the in-path IP address for the In-Path IP address? 10.11.11.6
Edge appliance.
Step 15: In-Path Netmask? Enter the in-path netmask address. In-Path Netmask? 255.255.0.0
Step 16: In-Path Default Enter the in-path default gateway In-Path Default Gateway?
10.11.11.16
gateway? (the WAN gateway).
Step 17: Set the in-path: LAN Enter the in-path, LAN interface Set the in-path: LAN interface
speed? [auto] auto
interface speed? speed. Make sure that this value
matches the setting on your router or
switch.
The default value is auto.
Step 18: Set the in-path: LAN Enter the in-path, LAN duplex value. Set the in-path: LAN interface
duplex? [auto] auto
interface duplex? Make sure that this value matches
the setting on your router or switch.
The default value is auto.
Step 19: Set the in-path: WAN Enter the in-path, WAN interface Set the in-path: WAN interface
speed? [auto] auto
interface speed? speed. Make sure that this value
matches the setting on your router or
switch.
The default value is auto.
Step 20: Set the in-path: WAN Enter the in-path, WAN duplex Set the in-path: WAN interface
duplex? [auto] auto
interface duplex? speed. Make sure that this value
matches the setting on your router or
switch.
The default value is auto.
The Edge appliance configuration wizard automatically saves your configuration settings.
8. To log out of the system, enter this command at the system prompt:
amnesiac> exit
For detailed information about the CLI, see the Riverbed Command-Line Interface Reference Manual.
1. Verify that you can connect to the CLI using one of these devices:
An ASCII terminal or emulator that can connect to the serial console. It must have the following
settings: 9600 bps, 8 bits, no parity, 1 stop bit, vt100, and no flow control.
A computer with a Secure Shell (SSH) client that is connected to the Edge appliance Primary
port.
or
ssh admin@<ip-address>
3. You are prompted for the administrator password. This is the password you set in the configuration
wizard.
If you have problems connecting to the SteelFusion Edge (SFE), use this flow chart to troubleshoot
issues.
Figure 3-12. Resolving IP connectivity
Note: Before you begin, clear your browser cache and cookies to ensure the user interface displays correctly.
1. Specify the URL for the Management Console in the location box of your web browser:
<protocol>://<host>.<domain>
The <protocol> variable is http or https. HTTPS uses the Secure Socket Layer (SSL) protocol to
ensure a secure environment. When you connect using HTTPS, the system prompts you to inspect
and verify the SSL certificate. This is a self-signed certificate that provides encrypted web
connections to the Management Console. The system re-creates the certificate when you change
the appliance hostname or when the certificate expires.
The secure vault does not protect the self-signed certificate used with HTTPS connections.
The <host> variable s the hostname you assigned to the Edge appliance primary interface in the
configuration wizard. If your DNS server maps that IP address to a name, you can specify the DNS
name.
The <domain> variable is the full domain name for the appliance.
Note: Alternatively, you can specify the IP address instead of the host and domain name.
2. In the Username text box, specify the user login: admin, monitor, a login from a RADIUS or TACACS+
database, or any local accounts created using the Role-Based Accounts feature. The default login
is admin.
Users with administrator (admin) privileges can configure and administer the Edge. Users with
monitor (monitor) privileges can view the Edge reports and user logs and change their own
password. A monitor user cannot make configuration changes.
3. In the Password text box, type the password you assigned in the configuration wizard of the Edge
appliance. (The default administrator password for the Edge is password.)
To verify optimization
1. Choose Optimization > Reports: Bandwidth Optimization in the Management Console to verify
optimization.
3. Drag and drop a 1-MB file from the client to the remote server.
Ensure that the server is located across the WAN.
1. In the Management Console, choose Administration > Diagnostics: System Logs to display the
System Logs page.
If you find errors, change the speed and duplex settings on your LAN and WAN interface in the
Configure > Networking: Inpath 0_0 page.
Next steps
This table summarizes the next steps you should take to configure the Edge appliance.
Task Reference
If you are using a SteelFusion Core for storage, you Choose Storage > Storage Edge Configuration.
should configure and connect it before running the
For details, see the SteelFusion Edge Management
Hypervisor Installer. A SteelFusion Core allows you
Console User’s Guide.
to access remote storage at your data center and
make that storage available to your hypervisor.
Set up the hypervisor using the Hypervisor Installer. Choose Virtualization > Hypervisor: Installer.
The Installer guides you through the initial
For details, see the SteelFusion Edge Management
configuration of the hypervisor.
Console User’s Guide.
After you run the Installer, you can customize the
hypervisor password. You can also monitor the
current status and resource allocation from the
Installer.
Connect the SteelFusion Edge to the SteelFusion Choose Storage > Storage Edge Configuration.
Core.
For details, see the SteelFusion Edge Management
You can also optionally connect the Edge to another Console User’s Guide.
active Edge as a standby peer for high availability.
Configure networking and optimization features. For details, see the SteelFusion Edge Management
Console User’s Guide.
Caution: Read and follow the safety guidelines described in the Safety and Compliance Guide. Failure to follow
these safety guidelines can result in damage to the equipment.
For detailed information about installing the appliance to a rack, see the SteelFusion Edge Hardware
and Maintenance Guide.
For detailed information about your deployment options and best practices for deploying Edge
appliances, see the SteelFusion Design Guide.
Figure 4-1. SteelFusion Edge in-path deployment
You can also deploy the Edge appliance for high availability (HA) where Edge and Core appliances are
deployed as pairs so that if either peer fails, the surviving Edge or Core appliances can take over. We
strongly recommend that you deploy Edge appliances as pairs in an HA cluster configuration. For
detailed information about HA, see the SteelFusion Edge Management Console User’s Guide and the
SteelFusion Design Guide.
Figure 4-2. SteelFusion Edge high availability deployment
You must always connect the Edge appliance using either the cable in the accessories box or
another cable that is approved for use by the IEC in the country in which the appliance is
connected.
You cannot connect the Edge appliance directly to multiphase outlets. You must use a rack power
distribution unit (PDU) or power strip that provides the appropriate three-prong outlet (hot/
neutral/ground). For details, see the Knowledge Base solution number S13425.
One Phillips screwdriver
Rails
One mounting kit
Documentation kit
If any items are damaged or missing, notify Riverbed Support at https://support.riverbed.com for
replacement or repair.
Site requirements
Before you install the Edge appliance, make sure that your site meets these requirements:
It is a standard electronic environment where the ambient temperature does not exceed 104ºF
(40ºC) and the relative humidity does not exceed 80% (noncondensing). For detailed information,
see the SteelFusion Edge Hardware and Maintenance Guide.
Ethernet connections are available within the standard Ethernet limit.
There is available space on a two-post or four-post 19-inch rack. For details about installing the
Edge to a rack, see the Rack Installation Guide or the printed instructions that were shipped with
the appliance.
A clean power source is available, dedicated to computer devices and other electronic equipment.
The rack is a standard 19-inch Telco-type mounting rack.
Before you begin, consult the SteelFusion Edge Hardware and Maintenance Guide for detailed
information about how to install your model to a rack.
Note: We recommend that you use a four-post mounting rack for 2U appliances.
Note: If your rack requires special mounting screws, contact your rack manufacturer.
Port Description
PRI The primary port connects the Edge appliance to a LAN switch. This interface enables
(Primary) you to connect to the Edge Management Console and the SteelFusion Edge CLI.
This interface can also be used to connect the SteelFusion Core through the RiOS
node, in-path interface.
The primary and auxiliary ports cannot share the same network subnet.
LAN 1_0 (1U) This port connects the LAN port of the Edge appliance to the LAN switch using a
LAN 0_0 (2U) straight-through cable.
The Edge appliance uses one or more in-path interfaces to provide Ethernet network
connectivity for optimized traffic. Each in-path interface comprises two physical
ports: the LAN port and the WAN port. Use the LAN port to connect the Edge appliance
to the internal network of the branch office.
If the Edge appliance is deployed between two switches, both the LAN and WAN ports
must be connected with straight-through cables.
WAN 1_0 (1U) This port connects the WAN port of the Edge appliance to the WAN router using a
WAN 0_0 (2U) crossover cable.
The WAN port is the second of two ports that compose the in-path interface. The WAN
port is used to connect the Edge appliance toward WAN-facing devices such as a
router, firewall, or other equipment located at the WAN boundary.
If you require additional in-path interfaces or require 10GigE or Fiber connectivity, you
can install a bypass NIC in the RiOS node expansion slot.
eth0_0, eth0_1 These ports provide additional iSCSI interfaces for storage traffic to external servers
when used by the RiOS node.
The ports are connected to a LAN switch using a straight-through cable.
These ports can also provide SteelFusion Edge high availability (HA). In an HA
deployment, use these ports for BlockStream heartbeat and synchronization between
SteelFusion Edge HA peers. For detailed information about HA deployments, see the
SteelFusion Design Guide.
If you require additional connectivity in an HA deployment, install a supported
nonbypass NIC in the RiOS node expansion slot.
Port Description
RIOS COM A RiOS serial RJ45 communication port that manages the RiOS node. Serial settings:
9600 bps, 8 data bit, 1 stop bit, no parity.
Connects the serial cable to a terminal device. You establish a serial connection to a
terminal emulation program for console access to the configuration wizard and the
Edge CLI.
HYP COM A hypervisor serial RJ45 communication port used to manage the hypervisor node.
Serial settings: 9600 bps, 8 data bit, 1 stop bit, no parity.
VGA Optional Hypervisor VGA connector. This port is useful for BIOS, POST, and PXE
debugging.
Figure 4-3 and Figure 4-4 show the locations of the ports on the rear of the 1U and 2U appliances.
Figure 4-3. 1U back panel
Figure 4-5 shows typical branch office connections for the Edge appliance.
Figure 4-5. Typical SteelFusion Edge port connections 1U appliance
This table summarizes the NIC deployment options for the Edge appliance.
For detailed information about installing additional NICs, see the SteelFusion Edge Hardware and
Maintenance Guide and the SteelFusion Design Guide.
Netmask
DNS IP address
Administrator password
In-path netmask
In-path gateway
Caution: In European electrical environments, you must ground (earth) the green/yellow tab on the power cord or
risk electrical shock.
1. If your appliance has a master power switch, ensure that it is in the off position.
Device Cable
Edge appliance to a switch Straight-through (for example, primary and LAN ports on the appliance to the
LAN switch)
Edge appliance to a router Crossover (for example, WAN port on the appliance to the WAN router)
Edge appliance to a host Crossover (for example, LAN and WAN ports on the Edge appliance bypass
cards act like host interfaces during normal operation)
For detailed information about cabling best practices, see the SteelFusion Design Guide.
1. Plug the straight-through cable into the primary port of the appliance and the LAN switch. The
primary port can be any port on your LAN switch configured to connect to a host.
Figure 4-7. Connecting the primary port to the LAN switch
2. Identify the straight-through cable that connects your LAN switch to your WAN router. Unplug the
end connected to the WAN router.
Figure 4-8. Disconnecting the WAN router
3. Plug the straight-through cable that you disconnected from the WAN router into the LAN port of the
appliance.
Figure 4-9. Connecting the LAN switch to the LAN port
4. Using the provided crossover cable, plug the cable into the WAN port of the appliance and the WAN
router.
Figure 4-10. Connecting the WAN port to the WAN router
Note: If you have additional four-port bypass cards, repeat Step 1 through Step 4. For detailed information about
installing additional bypass cards, see the Network and Storage Card Installation Guide and the SteelFusion Edge
Hardware and Maintenance Guide.
1. Plug the straight-through cable into one of the hypervisor ports: gbe0_0, gbe0_1, gbe0_2, or
gbe0_3.
2. Plug the straight-through cable into any switch that is connected to the hypervisor node.
The interface you configured as an Edge VIP should be connected to the same LAN switch to which
you connected the hypervisor port (gbe0_x).
3. After you complete the configuration process for the Edge appliance, configure and connect the
SteelFusion Core. Core allows you to access remote storage at your data center and make that
storage available to your hypervisor. For details, see the SteelFusion Core Management Console
User’s Guide.
4. Connect to the Edge Management Console to configure your hypervisor with the Hypervisor
Installer.
You can access the Hypervisor Installer from the Edge Dashboard or by choosing Virtualization >
Installer: Installer.
Note: The hypervisor must be installed before you can host VMs.
1. Plug the serial cable into the RiOS COM port and a terminal.
Figure 4-11. Connecting to the SteelFusion Edge
2. Start your terminal emulation program, such as Tera Term Pro. The terminal device must have these
settings:
Baud rate: 9600 bps
Data bits: 8
Parity: none
Stop bits: 1
vt100 emulation
No flow control
If you are using the Edge appliance with a terminal server, the terminal server must use hardware
flow control for the port connected to the Edge appliance.
We recommend that you connect the console port to a device that logs output to help identify
problems with the system.
3. Log in as administrator user (admin) and enter the default password (password). For example:
login as: admin
Sent username "admin"
password: password
The configuration wizard automatically starts after you have entered the login and default
password. After you have established a connection, you configure the Edge appliance using the
configuration wizard.
4. If you have a SteelCentral Controller for SteelHead (SCC) appliance installed in your network to
manage multiple Edge appliances, you can use it to automatically configure them:
Do you want to auto-configure using a SCC? no
If you answer yes, you are prompted for the SCC hostname or IP address. The hostname or IP
address is used to contact the SCC. The default value is riverbedcmc. If you enter no, the wizard
continues.
Note: If you mistakenly answer yes, to return to the wizard from the CLI, enter the configuration jump-start
command from configuration mode. For detailed information, see “To restart the configuration wizard” on page 62.
5. To start the configuration wizard, type yes at the system prompt and press Enter.
Do you want to use the configuration wizard for initial configuration? yes
Note: Press ? for help; press Ctrl+B to go back to the previous step.
6. Complete the configuration wizard steps on the branch office Edge appliance as described in this
table.
Step 1: Host name? Enter the hostname for the Edge hostname? amnesiac
appliance.
Step 2: Use DHCP on the You are given the option to enable Use DHCP? no
primary interface? the DHCP to automatically assign an
IP address to the primary interface
for the Edge appliance.
We recommend that you do not set
DHCP.
The default value is no.
Step 3: Primary IP address? Enter the IP address for the Edge Primary IP address? 10.10.10.6
appliance.
Step 5: Default gateway? Enter the default gateway for the Default gateway? 10.0.0.1
Edge appliance.
Step 6: Primary DNS server? Enter the primary DNS server IP Primary DNS server? 10.0.0.2
address.
Step 7: Domain name? Enter the domain name for the Domain name? example.com
network where the Edge appliance is
to reside.
If you set a domain name, you can
enter hostnames in the system
without the domain name.
Step 8: Admin password? We strongly recommend that you Admin password? xxxyyy
change the default administrator
password at this time. The password
must be a minimum of six
characters.
The default administrator password
is password.
Step 9: SMTP server? Enter the name of the SMTP server. SMTP server? natoma
External DNS and external access
for SMTP traffic is required for email
notification of events and failures to
function.
Step 10: Notification email Enter a valid email address to which Notification email address?
example@xample.com
address? notification of events and failures
are to be sent.
Step 11: Set the primary Enter the speed on the primary Set the primary interface speed?
[auto] auto
interface speed? interface (that is, the Edge
appliance). Make sure that this value
matches the setting on your router or
switch.
The default value is auto.
Step 12: Set the primary Enter the duplex mode on the Set the primary interface
duplex? [auto] auto
interface duplex? primary interface. Make sure that
this value matches the setting on
your router or switch. The default
value is auto.
Step 13: Would you like to Enter yes at the system prompt to Would you like to activate the
in-path configuration? yes
activate the in-path configure in-path support. An in-
configuration? path configuration is a configuration
in which the Edge appliance is in the
direct path of the client and server.
Step 14: In-Path IP address? Enter the in-path IP address for the In-Path IP address? 10.11.11.6
Edge appliance.
Step 15: In-Path Netmask? Enter the in-path netmask address. In-Path Netmask? 255.255.0.0
Step 16: In-Path Default Enter the in-path default gateway In-Path Default Gateway?
10.11.11.16
gateway? (the WAN gateway).
Step 17: Set the in-path: LAN Enter the in-path, LAN interface Set the in-path: LAN interface
speed? [auto] auto
interface speed? speed. Make sure that this value
matches the setting on your router or
switch.
The default value is auto.
Step 18: Set the in-path: LAN Enter the in-path, LAN duplex value. Set the in-path: LAN interface
duplex? [auto] auto
interface duplex? Make sure that this value matches
the setting on your router or switch.
The default value is auto.
Step 19: Set the in-path: WAN Enter the in-path, WAN interface Set the in-path: WAN interface
speed? [auto] auto
interface speed? speed. Make sure that this value
matches the setting on your router or
switch.
The default value is auto.
Step 20: Set the in-path: WAN Enter the in-path, WAN duplex Set the in-path: WAN interface
duplex? [auto] auto
interface duplex? speed. Make sure that this value
matches the setting on your router or
switch.
The default value is auto.
The Edge appliance configuration wizard automatically saves your configuration settings.
8. To log out of the system, enter this command at the system prompt:
amnesiac> exit
For detailed information about the CLI, see the Riverbed Command-Line Interface Reference Manual.
1. Verify that you can connect to the CLI using one of these devices:
An ASCII terminal or emulator that can connect to the serial console. It must have the following
settings: 9600 bps, 8 bits, no parity, 1 stop bit, vt100, and no flow control.
A computer with a Secure Shell (SSH) client that is connected to the Edge appliance Primary
port.
or
ssh admin@<ip-address>
3. You are prompted for the administrator password. This is the password you set in the configuration
wizard.
If you have problems connecting to the SteelFusion Edge (SFE), use this flow chart to troubleshoot
issues.
Figure 4-12. Resolving IP connectivity
Note: Before you begin, clear your browser cache and cookies to ensure the user interface displays correctly.
1. Specify the URL for the Management Console in the location box of your web browser:
<protocol>://<host>.<domain>
The <protocol> variable is http or https. HTTPS uses the Secure Socket Layer (SSL) protocol to
ensure a secure environment. When you connect using HTTPS, the system prompts you to inspect
and verify the SSL certificate. This is a self-signed certificate that provides encrypted web
connections to the Management Console. The system re-creates the certificate when you change
the appliance hostname or when the certificate expires.
The secure vault does not protect the self-signed certificate used with HTTPS connections.
The <host> variable s the hostname you assigned to the Edge appliance primary interface in the
configuration wizard. If your DNS server maps that IP address to a name, you can specify the DNS
name.
The <domain> variable is the full domain name for the appliance.
Note: Alternatively, you can specify the IP address instead of the host and domain name.
2. In the Username text box, specify the user login: admin, monitor, a login from a RADIUS or TACACS+
database, or any local accounts created using the Role-Based Accounts feature. The default login
is admin.
Users with administrator (admin) privileges can configure and administer the Edge. Users with
monitor (monitor) privileges can view the Edge reports and user logs and change their own
password. A monitor user cannot make configuration changes.
3. In the Password text box, type the password you assigned in the configuration wizard of the Edge
appliance. (The default administrator password for the Edge is password.)
To verify optimization
1. Choose Optimization > Reports: Bandwidth Optimization in the Management Console to verify
optimization.
3. Drag and drop a 1-MB file from the client to the remote server.
Ensure that the server is located across the WAN.
1. In the Management Console, choose Administration > Diagnostics: System Logs to display the
System Logs page.
If you find errors, change the speed and duplex settings on your LAN and WAN interface in the
Configure > Networking: Inpath 0_0 page.
Next steps
This table summarizes the next steps you should take to configure the Edge appliance.
Task Reference
Connect the SteelFusion Edge to the SteelFusion Choose Storage > Storage Edge Configuration.
Core.
For details, see the SteelFusion Edge Management
You can also optionally connect the Edge to another Console User’s Guide.
active Edge as a standby peer for high availability.
Configure the SteelFusion Core storage. Core allows In the SteelFusion Core Management Console, choose
you to access remote storage at your data center Configure > NFS: Exports.
and make that storage available to your hypervisor.
For details, see the SteelFusion Core Management
Map the NFS exports to the Edge and specify the Console User’s Guide.
exports to install onto the VSP ESXi hypervisor.
Set up the hypervisor using the Hypervisor Installer. Choose Virtualization > Hypervisor: Installer.
The Installer guides you through the initial
For details, see the SteelFusion Edge Management
configuration of the hypervisor.
Console User’s Guide.
After you run the Installer, you can customize the
hypervisor password. You can also monitor the
current status and resource allocation from the
Installer.
Connect another Edge for high availability. For details, see the SteelFusion Edge Management
Console User’s Guide.
Configure networking and optimization features. For details, see the SteelFusion Edge Management
Console User’s Guide.