Steelhead® Appliance Installation and Configuration Guide

5/27/2018 Steelhead Appliance Installation and Configuration Guide

Steelhead

Appliance Installation andConfiguration Guide

SteelheadEX (Series xx60)

Version 1.0.0

June 2012


Riverbed Technology199 Fremont StreetSan Francisco, CA 94105

Fax: 415.247.8801

Web: http://www.riverbed.com

Phone: 415.247.8800

Part Number

712-00110-01

2012 Riverbed Technology. All rights reserved.

Riverbed, Cloud Steelhead, Granite, Interceptor, RiOS, Steelhead, Think Fast, Virtual Steelhead, Whitewater,Mazu, Cascade, Cascade Pilot, Shark, AirPcap, SkipWare, TurboCap, WinPcap, Wireshark, and Stingray aretrademarks or registered trademarks of Riverbed Technology, Inc. in the United States and other countries. Riverbed and anyRiverbed product or service name or logo used herein are trademarks of Riverbed Technology. All other trademarks used herein

belong to the ir respective owners . The trade marks and logos displayed herein cannot be used without the prior written consentof Riverbed Technology or their respective owners.

Akamai and the Akamai wave logo are registered trademarks of Akamai Technologies, Inc. Sur eRoute is a service mark ofAkamai. Apple and Mac are registered trad emarks of Apple, Incorporated in the United States and in other countries. Cisco is aregistered trademark of Cisco Systems, Inc. and its affiliates in the United States and in other countries. EMC, Symmetrix, andSRDF are registered trademarks of EMC Corporation and its affiliates in the United States and in other countries. IBM, iSeries, andAS/400 are registered trademarks of IBM Corporation and its affiliates in the United States and in other countries. Linux is atrademark of Linus Torvalds in the United States and in other countries. Microsoft, Windows, Vista, Outlook, and InternetExplorer are trademarks or registered trademarks of Microsoft Corporation in the United States and in other countries. Oracle and

JInitiator a re tra demark s or r egistered trademarks of O racle C orpora tion in the United States and in other countr ies. UNIX is aregistered trademark in the United States and in other countries, exclusively licensed through X/Open Company, Ltd. VMwar e,ESX, ESXi are trademarks or registered trademarks of VMware, Incorporated in the United States and in other countries.

This product includes software developed by the University of California, Berkeley (and its contributors), EMC, and ComtechAHA Corporation. This product is derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm.

NetApp Manageability Software Development Kit (NM SDK), including any third-party software available for review with suchSDK which can be found at http://communities.netapp.com/docs/DOC-3777, and are included in a NOTICES file includedwithin the downloaded files.

For a list of open source software (i ncluding libraries) used in the development of this software along with associated copyrightand license agreements, see the Riverbed Support site at https//support.riverbed.com. You must log in to Riverbed Support toview this information.

This documentation is furnished AS I S and is subject to change without notice and should not be construed as a commitmentby Riverbed Technology. This docume ntation may not be copied, modif ied or dist ributed wi thout the express authorization ofRiverbed 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 accordanc e with the Federal AcquisitionRegulations as applied to civilian agencies and the Defense Federal Acquisition Regulation Supplement as applied to militaryagencies. This documentation qualifies as commercial computer software documentation and any use by the government shall

be governed solely by the se terms . All other use is prohibited. Riverbed Technology assumes no r esponsibility or liab ility for anyerrors or inaccuracies that may appear in this documentation.

Part Number

712-00110-01


Steelhead Appliance Installation and Configuration Guide iii

Contents

Preface.........................................................................................................................................................1

About This Guide .............. ................ ............... .............. ................ .............. ............... ............. ................ .....1

Audience..................................................................................................................................................1

Document Conventions.........................................................................................................................2Product Dependencies and Compatibility.................................................................................................2

Hardware and Software Dependencies...............................................................................................3

CMC Compatibility................................................................................................................................3

Virtual Services Platform (VSP) Support ............. ............... .............. ............... .............. ............... ......3

Firewall Requirements...........................................................................................................................3

Ethernet Network Compatibility .............. ................ .............. ................ ............... ................ ..............4

SNMP-Based Management Compatibility..........................................................................................4

Antivirus Compatibility ................ .............. ................ ................ .............. ................ ................ ............5

Additional Resources .............. ............... .............. ................ ............... .............. ............... ............. ................5

Release Notes ..........................................................................................................................................5

Riverbed Documentation and the Support Knowledge Base .............. ................ ............... .............6Safety Guidelines .............. ............... .............. ................ ............. ................ ............. ................ ................. .....6

Contacting Riverbed......................................................................................................................................6

Internet.....................................................................................................................................................6

Technical Support .............. ............... ............... .............. ............... .............. ............... ............. ................6

Professional Services ............. ................ .............. ............... ................ .............. ............... ................ .......6

Documentation........................................................................................................................................7

Chapter 1 - Overview of the Steelhead EX ...............................................................................................9

WAN Optimization........................................................................................................................................9

Auto-Discovery Process.......................................................................................................................11Configuring Optimization...................................................................................................................11

Fail-to-Wire (Bypass) Mode.................................................................................................................12

Fail-to-Block (Disconnect) Mode........................................................................................................13

Virtual Services Platform (VSP).................................................................................................................13

VSP Packages ........................................................................................................................................14

Virtual Network Interfaces (VNIs).....................................................................................................14

Granite Branch Storage ............... ............. ............... .............. ............... ................ ............. ............ ..............15


iv Steelhead Appliance Installation and Configuration Guide

Contents

How Granite Works..............................................................................................................................15

System Architecture ............. .............. ................ ............... .............. ............... ............... ............... ........16

Granite-Dedicated Target Mode ............. ............... .............. ............... ............. ................ ................ ..........17

Chapter 2 - Managing Riverbed Licenses ..............................................................................................19

Riverbed Licensing Methods ............. ............... ................ .............. ............... ................ ............. ............. ..19

Automatic Licensing .............. ................ .............. ................ ............... .............. ................ .............. ............20

Retrieving Licenses Using the Riverbed Licensing Portal.....................................................................21

Installing Your License Keys...............................................................................................................23

Chapter 3 - Installing and Configuring the Steelhead Appliance.........................................................25

Choosing a Network Deployment ............. .............. ................ ............... .............. ................ ............... .....25

Checking Your Inventory............................................................................................................................27

Preparing Your Site for Installation...........................................................................................................28

Completing the Configuration Checklist ................................................................................................29

Steelhead Appliance Ports...................................................................................................................30

Bypass Card Interface Naming Conventions ............... .............. ............... .............. ............... ..........30

Powering On the Steelhead Appliance.....................................................................................................31

Connecting to the Steelhead Appliance ............... .............. ............... ................ .............. ............... ..........32

Configuring In-Path Steelhead Appliances ............... .............. ................ ............... .............. ................ ...33

Avoiding Duplex Mismatch................................................................................................................33

Configuration Wizard ................ ............. ................ ............. ................ ............... .............. ................ ...33

Connecting the Steelhead Appliance to Your Network..................................................................37

Verifying Your Connections .............. ................ ............... .............. ................ ................ ............. ........38

Connecting to the Management Console..........................................................................................40Verifying Your Configuration ............. .............. ................ ................ .............. ............... ................ .....41

Configuring Out-of-Path Steelhead Appliances .............. ............... .............. ............... ................ ...........42

Before You Begin...................................................................................................................................42

Connecting the Steelhead Appliance to Your Network..................................................................45

Configuring the Client-Side Appliance.............................................................................................45

Chapter 4 - Troubleshooting....................................................................................................................47

Cables ............................................................................................................................................................47

Solution ............. ............... .............. ............... ................ ............. ................ ............... ............ .............. ...48

Duplex Mismatch.........................................................................................................................................48Possible Cause.......................................................................................................................................48

Example..................................................................................................................................................48

Solutions.................................................................................................................................................49

In-Path Steelhead Appliances Connection...............................................................................................49

Possible Cause.......................................................................................................................................49

Solutions.................................................................................................................................................49

Oplock Issues................................................................................................................................................49


Steelhead Appliance Installation and Configuration Guide v

Contents

Possible Causes ................ ............... .............. ................ ............... .............. ................ ............. ..............50

Example..................................................................................................................................................50

Solutions.................................................................................................................................................50

CIFS Overlapping Open Optimization Denies Multi-User Access ................ ................ ................. .....51

Solution ............. ............... .............. ............... ................ ............. ................ ............... ............ .............. ...51

IP Address Configuration...........................................................................................................................52Solutions.................................................................................................................................................52

Asymmetric Routing ............. .............. ............... ............... .............. ................ ............. ................ ...............53

Possible Cause.......................................................................................................................................53

Solutions.................................................................................................................................................53

Packet Ricochet.............................................................................................................................................53

Possible Cause.......................................................................................................................................54

Solutions.................................................................................................................................................54

Packet RicochetInternet Control Messaging Protocol (ICMP) Redirects.........................................54

Possible Causes.....................................................................................................................................54

Solutions.................................................................................................................................................54

Simplified Routing.......................................................................................................................................55

Auto-Discovery Failure...............................................................................................................................56

Possible Causes.....................................................................................................................................56

Solutions.................................................................................................................................................56

Protocol Optimization Errors.....................................................................................................................56

Solutions.................................................................................................................................................57

Server-Side Out-of-Path Connection Caveats..........................................................................................57

Specific Problems.........................................................................................................................................57

Resetting a Lost Password..........................................................................................................................58

Network Integration Checklist ............... ................ ................ .............. ................ ................ ............. ........59

Appendix A - Series EX xx60 Technical Specifications ........................................................................61

VSP and Granite Memory and Storage Specifications .............. .............. ............... ............. ................ ...62

VSP Memory Specifications .............. ............... ................ ............. ................ ............. ............... ..........62

VSP and Granite Storage Specifications............................................................................................62

1U EX560 and EX760 Status Lights and Ports ............. ............... .............. ............... ............. ............... ....63

System LEDs..........................................................................................................................................64

1U EX1160 Status Lights and Ports .............. ............... .............. ............... ............. ................ ............... .....66

System LEDs..........................................................................................................................................66

2U EX1260 Status Lights and Ports .............. ............... .............. ............... ............... .............. ............... .....67

System LEDs..........................................................................................................................................68

EX560 and EX760 Technical Specifications ................ ............. ................ ............. ............... .............. .......69

Power Requirements and Consumption...........................................................................................69

EX560 with Granite Technical Specifications...........................................................................................70

EX1160 and EX1260 Technical Specifications...........................................................................................70
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


vi Steelhead Appliance Installation and Configuration Guide

Contents

EX1160 and EX1260 with Granite Technical Specifications .............. ............... ................ .............. ........71

EX1160 and EX1260 Power Requirements and Consumption ............. ................ ............. ................ ....71

CPU Specifications.......................................................................................................................................72

Environmental Specifications ................ ............... .............. ............... .............. ............... ............. ..............72

Index ..........................................................................................................................................................73


Steelhead Appliance Installation and Configuration Guide 1

Preface

Welcome to the Steelhead Appliance Installation and Configuration Guidefor Steelhead EX appliances.Read thispreface for an overview of the information provided in this guide and for an understanding of thedocumentation conventions used throughout.

About This Guide

The Steelhead Appliance Installation and Configuration Guidedescribes how to install and configure theSteelhead EX appliance (Steelhead appliance).

Audience

This guide is written for storage and network administrators familiar with administering and managingWANs using common network protocols such as TCP, CIFS, HTTP, FTP, and NFS.


2 Steelhead Appliance Installation and Configuration Guide

Preface Product Dependencies and Compatibility

Document Conventions

This manual uses the following standard set of typographical conventions to introduce new terms, illustratescreen displays, describe command syntax, and so forth.

Product Dependencies and Compatibility

This section provides information about product dependencies and compatibility. It includes the following

information: Hardware and Software Dependencies, next

CMC Compatibility on page 3

Virtual Services Platform (VSP) Support on page 3

Ethernet Network Compatibility on page 4

SNMP-Based Management Compatibility on page 4

Antivirus Compatibility on page 5

Convention Meaning

italics Within text, new terms and emphasized words appear in italic typeface.

boldface Within text, CLI commands and GUI controls appear in bold typeface.

Courier Code examples appear in Courier font:

amnesiac > enableamnesiac # configure terminal

< > Values that you specify appear in angle brackets:

interface

[ ] Optional keywords or variables appear in brackets:

ntp peer [version ]

{ } Required keywords or variables appear in braces:{delete | upload }

| The pipe symbol represents a choice between the keyword or variable to the left or right ofthe symbol (the keyword or variable can be either optional or required):

{delete | upload }



Product Dependencies and Compatibility Preface

Hardware and Software Dependencies

The following table summarizes the hardware and software requirements for the Steelhead appliance.

CMC Compatibility

The Steelhead appliance has been tested with the following Central Management Console (CMC) version.

Virtual Services Platform (VSP) Support

In RiOS v7.0.1 and later, VSP is supported only on the EX Series xx60 hardware platforms.

Firewall Requirements

Riverbed recommends that you deploy the Steelhead appliance behind your firewall. The followingfirewall settings are required for the Steelhead appliance:

Ports 7800 and 7810 must be open.

Make sure your firewall does not strip TCP options.

If you have the Granite option enabled, ports 7950-7954 must be open.

Riverbed Component Hardware and Software Requirements

Steelhead EX appliance 19-inch (483 mm) four-post rack.

RiOS v7.0.1

CMC v6.5.3

VMware Server 2.0.2

Steelhead Management Console Any computer that supports a Web browser with a colorimage display.

The Management Console has been tested with MozillaFirefox version v3.0.x or later, and Microsoft InternetExplorer version v6.x and v7.x or later

Note: JavaScript and cookies must be enabled in yourWeb browser.

Steelhead RiOS Version Recommended CMCVersion

v7.0.1 v6.5.3

v7.0.3 v7.0



Preface Product Dependencies and Compatibility

Ethernet Network Compatibility

The Steelhead appliance supports the following Ethernet networking standards:

Ethernet Logical Link Control (LLC) (IEEE 802.2 - 1998)

Fast Ethernet 100 Base-TX (IEEE 802.3 - 2008)

Gigabit Ethernet over Copper 1000 Base-T and Fiber 1000 Base-SX (LC connector) and Fiber 1000 BaseLX (IEEE 802.3 - 2008)

10 Gigabit Ethernet over Fiber 10GBase-LR Single Mode and 10GBase-SR Multimode (IEEE 802.3 -2008)

The Steelhead appliance ports support the following connection types and speeds:

Primary- 10/100/1000 Base-T, auto-negotiating

Auxiliary- 10/100/1000 Base-T, auto-negotiating

LAN- 10/100/1000 Base-TX or 1000 Base-SX or 1000 Base-LX or 10GBase-LR or 10GBase-SR,depending on configuration

WAN- 10/100/1000 Base-TX or 1000 Base-SX or 1000 Base-LX or 10GBase-LR or 10GBase-SR,depending on configuration

The Steelhead appliance supports VLAN Tagging (IEEE 802.3 - 2008). It does not support the ISL protocol.

All copper interfaces are auto-sensing for speed and duplex (IEEE 802.3 - 2008).

The Steelhead appliance auto-negotiates speed and duplex mode for all data rates and supports full duplexmode and flow control (IEEE 802.3 - 2008).

The Steelhead appliance with a Gigabit Ethernet card supports jumbo frames on in-path and primary ports.

SNMP-Based Management Compatibility

The Steelhead appliance supports a proprietary Riverbed MIB accessible through SNMP. SNMP v1 (RFCs1155, 1157, 1212, and 1215) and SNMP v2c (RFCs 1901, 2578, 2579, 2580, 3416, 3417, and 3418) are supported,even though some MIB items can only be accessible through SNMPv2.

SNMP support allows the Steelhead appliance to be integrated into network management systems such asHewlett Packard OpenView Network Node Manager, BMC Patrol, and other SNMP-based networkmanagement tools.



Additional Resources Preface

Antivirus Compatibility

The Steelhead appliance has been tested on clients and file servers generating CIFS traffic with thefollowing antivirus software with no impact on performance:

Network Associates (McAfee) VirusScan v7.0.0 Enterprise on the server

Network Associates (McAfee) VirusScan v7.1.0 Enterprise on the server Network Associates (McAfee) VirusScan v7.1.0 Enterprise on the client

Symantec (Norton) AntiVirus Corporate Edition v8.1 on the server

The Steelhead appliance has been tested on clients and file servers generating CIFS traffic with thefollowing antivirus software with moderate impact on performance:

F-Secure Anti-Virus v5.43 on the client

F-Secure Anti-Virus v5.5 on the server

Network Associates (McAfee) NetShield v4.5 on the server

Network Associates VirusScan v4.5 for multiple platforms on the client

Symantec (Norton) AntiVirus Corporate Edition v8.1 on the client

Additional Resources

This section describes resources that supplement the information in this guide. It contains the followingsections:

Release Notes, next

Riverbed Documentation and the Support Knowledge Base on page 6

Release Notes

The following online file supplements the information in this manual. It is available on the RiverbedSupport site at https://support.riverbed.com.

Examine this file before you begin the installation and configuration process. It contains importantinformation about this release of the Steelhead appliance.

Online File Purpose

_.pdf

Describes the product release and identifies fixed problems,known problems, and workarounds. This file also providesdocumentation information not covered in the manuals or thathas been modified since publication.



Preface Safety Guidelines

Riverbed Documentation and the Support Knowledge Base

For a complete list and the most current version of Riverbed documentation, log in to the Riverbed Supportsite at https://support.riverbed.com.

The Riverbed Knowledge Base is a database of known issues, how-to documents, system requirements, andcommon error messages. You can browse titles or search for keywords and strings.

To access the Riverbed Knowledge Base, log in to the Riverbed Support site athttps://support.riverbed.com.

Safety Guidelines

Follow the safety precautions outlined in the Safety and Compliance Guidewhen installing and setting upyour equipment.

Important: Failure to follow these safety guidelines can result in injury or damage to the equipment. Mishandling ofthe 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 thisrequirement applies to your country, consult the Safety and Compliance Guide. Before you install, operate, orservice the Riverbed products, you must be familiar with the safety information. Refer to the Safety andCompliance Guideif you do not clearly understand the safety information provided in this guide.

Contacting Riverbed

This section describes how to contact departments within Riverbed.

Internet

You can learn about Riverbed products through our Web site at http://www.riverbed.com.

Technical Support

If you have problems installing, using, or replacing Riverbed products, contact Riverbed Support or yourchannel 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

Riverbed has a staff of professionals who can help you with installation, provisioning, network redesign,project management, custom designs, consolidation project design, and custom coded solutions. To contactRiverbed Professional Services, email [email protected] or go to http://www.riverbed.com.
https://support.riverbed.com/https://support.riverbed.com/https://support.riverbed.com/https://support.riverbed.com/https://support.riverbed.com/https://support.riverbed.com/https://support.riverbed.com/https://support.riverbed.com/http://www.riverbed.com/http://www.riverbed.com/http://www.riverbed.com/http://www.riverbed.com/http://www.riverbed.com/https://support.riverbed.com/https://support.riverbed.com/https://support.riverbed.com/



Contacting Riverbed Preface

Documentation

We continually strive to improve the quality and usability of our documentation. We appreciate anysuggestions you may have about our online documentation or printed materials. Send documentationcomments to [email protected].



Preface Contacting Riverbed



CHAPTER 1 Overview of the Steelhead EX

The Steelhead EX series combines WAN optimization, virtualization, and storage consolidation to enableorganizations to meet the needs of the active branch office.

Each EX appliance combines WAN optimization and the Riverbed Virtual Services Platform (VSP), adedicated platform that runs virtual services and enables consolidation in branch offices.

Steelhead EX series can be upgraded to include Granite, the virtual edge of the data center that allows endusers in a branch to access and write to centralized storage over the WAN at local speeds.

This chapter provides an overview of the Steelhead EX. It includes the following sections:

WAN Optimization, next

Virtual Services Platform (VSP) on page 13

Granite Branch Storage on page 14

Granite-Dedicated Target Mode on page 16

WAN Optimization

The causes for slow throughput in WANs are well known: high delay (round-trip time or latency), limitedbandwidth, and chatty application protocols. Large enterprises spend a significant part of their informationtechnology budgets on storage and networks, much of it spent to compensate for slow throughput bydeploying redundant servers and storage and the required backup equipment. Steelhead appliances let youconsolidate and centralize key IT resources to save money, reduce capital expenditures, simplify keybusiness processes, and improve productivity.

With the Steelhead appliance, you can solve a range of problems affecting WANs and applicationperformance, including:

Insufficient WAN bandwidth Inefficient transport protocols in high-latency environments

Inefficient application protocols in high-latency environments

The Riverbed Optimization System (RiOS) intercepts client-server connections without interfering withnormal client-server interactions, file semantics, or protocols. All client requests are passed through to theserver normally, while relevant traffic is optimized to improve performance.

The optimization techniques RiOS utilizes are:



Overview of the Steelhead EX WAN Optimization

Data Streamlining- Steelhead appliances and Steelhead Mobile can reduce WAN bandwidthutilization by 65% to 98% for TCP-based applications using Data Streamlining. In addition totraditional techniques like data compression, RiOS also uses a Riverbed proprietary algorithm calledScalable Data Referencing (SDR). SDR breaks up TCP data streams into uniquedata chunksthat arestored in the hard disk (RiOSdata store) of the device running RiOS (a Steelhead appliance or SteelheadMobile host system). Each data chunk is assigned a unique integer label (reference)before it is sent to a

peer RiOS device across the WAN. When the same byte sequence is seen again in future transmissionsfrom clients or servers, the reference is sent across the WAN instead of the raw data chunk. The peerRiOS device (a Steelhead appliance or Steelhead Mobile host system) uses this reference to find theoriginal data chunk in its RiOS data store, and reconstruct the original TCP data stream.

Transport Streamlining- Steelhead appliances use a generic latency optimization technique calledTransport Streamlining. Transport Streamlining uses a set of standards and proprietary techniques tooptimize TCP traffic between Steelhead appliances. These techniques:

ensure that efficient retransmission methods, such as TCP selective acknowledgements, are used.

negotiate optimal TCP window sizes to minimize the impact of latency on throughput.

maximize throughput across a wide range of WAN links.

Application Streamlining- In addition to Data and Transport Streamlining optimizations, RiOS canapply application-specific optimizations for certain application protocols: for example, CIFs, MAPI,NFS, TDS, HTTP, Oracle Forms.

Management Streamlining- Management Streamlining refers to the methods that Riverbed hasdeveloped to simplify the deployment and management of RiOS devices. These methods include:

Auto-Discovery Process- Auto-discovery enables Steelhead appliances and Steelhead Mobile toautomatically find remote Steelhead appliances and to use them to optimize traffic. Auto-discoveryrelieves the burden of manually configuring large amounts of network information. The auto-discovery process enables administrators to control and secure connections, specify traffic to beoptimized, and specify peers for optimization.

Central Management Console (CMC)- The CMC enables remote Steelhead appliances to beautomatically configured and monitored. It also provides a single view of the overall benefit and

health of the Steelhead appliance network.

Steelhead Mobile Controller- TheMobile Controlleris the management appliance that tracks theindividual health and performance of each deployed software client, and to manage enterpriseclient licensing. The Mobile Controller enables you to see who is connected, view their datareduction statistics, and perform support operations such as resetting connections, pulling logs,and automatically generating traces for troubleshooting. You can perform all these managementtasks without end user input.



WAN Optimization Overview of the Steelhead EX

Typically, the Steelhead appliance is deployed on a LAN, with communication between appliances takingplace over a private WAN or VPN. Because optimization between Steelhead appliances typically takesplace over a secure WAN, it is not necessary to configure company firewalls to support specific ports for aSteelhead appliance .

Figure 1-1. Typical In-Path Deployment

For detailed information about how the Steelhead appliance works and deployment design principles, seethe Steelhead Appliance Deployment Guide.

Auto-Discovery Process

Auto-discovery enables Steelhead appliances to automatically find remote Steelhead appliances and tooptimize traffic to them. Auto-discovery relieves you of having to manually configure the Steelheadappliances with large amounts of network information: for example, multiple in-path rules. The auto-discovery process enables you to control and secure connections, specify which traffic is optimized, andspecify how remote peers are selected for optimization. There are two types of auto-discoveries, originaland enhanced.

Enhanced auto-discovery automatically discovers the last Steelhead appliance in the network path of theTCP connection. In contrast, the original auto-discovery protocol automatically discovers the first Steelheadappliance in the path. The difference is only seen in environments where there are three or more Steelheadappliances in the network path for connections to be optimized. Enhanced auto-discovery works withSteelhead appliances running the original auto-discovery protocol.

Configuring Optimization

You configure optimization of traffic using the Management Console or the Riverbed CLI. You configurewhat traffic a Steelhead appliance optimizes and specify the type of action it performs using:

In-Path rules- In-path rules determine the action a Steelhead appliance takes when a connection isinitiated, usually by a client. In-path rules are used only when a connection is initiated. Becauseconnections are usually initiated by clients, in-path rules are configured for the initiating, or client-sideSteelhead appliance. You configure one of the following types of in-path rule actions:

Auto- Use the auto-discovery process to determine if a remote Steelhead appliance is able tooptimize the connection attempting to be created by this SYN packet.

Pass-through- Allow the SYN packet to pass through the Steelhead appliance. No optimization isperformed on the TCP connection initiated by this SYN packet.

Fixed-Target- Skip the auto-discovery process and use a specified remote Steelhead appliance asan optimization peer. Fixed-target rules require the input of at least one remote target Steelheadappliance; an optional backup Steelhead appliance might also be specified.



Overview of the Steelhead EX WAN Optimization

Deny- Drop the SYN packet and send a message back to its source.

Discard- Drop the SYN packet silently.

Peering rules- Peering rules determine how a Steelhead appliance reacts when it sees a probe query.Peering rules are an ordered list of fields a Steelhead appliance uses to match with incoming SYNpacket fields: for example, source or destination subnet, IP address, VLAN, or TCP port, as well as the

IP address of the probing Steelhead appliance. This is especially useful in complex networks. There arethe following types of peering rule actions:

Pass- The receiving Steelhead appliance does not respond to the probing Steelhead appliance, andallows the SYN+ probe packet to continue through the network.

Accept- The receiving Steelhead appliance responds to the probing Steelhead appliance andbecomes the remote-side Steelhead appliance (that is, the peer Steelhead appliance) for theoptimized connection.

Auto- If the receiving Steelhead appliance is not using enhanced auto-discovery, this has the sameeffect as the Accept peering rule action. If enhanced auto-discovery is enabled, the Steelheadappliance only becomes the optimization peer if it is the last Steelhead appliance in the path to theserver.

For detailed information about in-path and peering rules and how to configure them, see the SteelheadManagement Console Users Guide.

Fail-to-Wire (Bypass) Mode

All Steelhead appliance models and in-path network interface cards support a fail-to-wire mode. In theevent of a failure or loss of power, the Steelhead appliance goes into bypass mode and the traffic passesthrough uninterrupted.

If the Steelhead appliance is in bypass mode, you are notified in the following ways:

The Intercept/Bypass status light on the bypass card is triggered. For detailed information aboutbypass card status lights, see the appendix.

The Home page of the Management Console displays Critical in the Status bar.

SNMP traps are sent (if you have set this option).

The event is logged to system logs (syslog).

Email notifications are sent (if you have set this option).

When the fault is corrected, new connections receive optimization; however, connections made during thefault do not. To force all connections to be optimized, enable the kickofffeature. Generally, connections areshort-lived and kickoff is not necessary. For detailed information about enabling the kickoff feature, see theSteelhead Management Console Users Guide.

When the Steelhead appliance is in bypass mode the traffic passes through uninterrupted. Traffic that wasoptimized might be interrupted, depending on the behavior of the application-layer protocols. When

connections are restored, they succeed, even though without optimization.

In an out-of-path deployment, if the server-side Steelhead appliance fails, the first connection from theclient fails. After detecting that the Steelhead appliance is not functioning, a ping channel is set up from theclient-side Steelhead appliance to the server-side Steelhead appliance. Subsequent connections are passedthrough unoptimized. When the ping succeeds, processing is restored and subsequent connections areintercepted and optimized.

For detailed information about the pingcommand, see the Riverbed Command-Line Interface ReferenceManual.



Virtual Services Platform (VSP) Overview of the Steelhead EX

Fail-to-Block (Disconnect) Mode

With fail-to-block mode enabled in a redundant network path environment, traffic is blocked and reroutedto an optimized backup path in the event of a failure.

This feature is useful only if the network has a routing or switching infrastructure that can automaticallydivert traffic off the link to the optimized backup path. In an active-backup redundant network setup, the

active path is configured to use fail-to-block, and the backup path is configured to use fail-to-bypass, thustraffic continues to be optimized on the backup path if there is a failure on the active path. In the event of afailure, the LAN and WAN interfaces power down and from a connected router or switch perspective thosedevices do not detect a link.

Steelhead EX supports fail-to-block mode on all cards.

The following events trigger fail-to-block if the feature is enabled:

Kernel crash

Hardware failure

Power loss

Note: You can use this with connection-forwarding, the allow-failureCLI command, and an additional Steelheadappliance on another path to the WAN to achieve redundancy. For more information, see the Riverbed Command-LineInterface Reference Manual.

You set fail-to-block mode in the Steelhead appliance CLI. For detailed information, see the SteelheadAppliance Deployment Guide.

Virtual Services Platform (VSP)

VSP is a VMware-based virtualization platform that provides the benefits of the most commonly deployedand advanced virtualization tool set. VSP is included in the native Steelhead EX appliance functionality anddoes not require a separate license.

VSP uses VMware Server 2.0.2 as the virtualization platform.In VSP, packaged virtual machines areinstalled in slots and run simultaneously as services directly from the Steelhead EX appliance. Servicesinclude in-band packages that sit in-line with optimization such as the Universal Threat Management(UTM) security services, proxy solutions such as video or network monitoring services, and improvedsupport for out-of-band packages like Windows Active Directory, DNS and DHCP management software,and print services.

VSP supports running up to five different virtual services on a single Steelhead EX appliance. However, youcan upload and store as many packages in a library as you want; the only limitation is the disk space on the

VSP partition.

In general, any virtual machine can be packaged and run as a service in VSP.

This section briefly describes the following:

VSP Packages, next

Virtual Network Interfaces (VNIs) on page 14

For details on configuring and using VSP, see the Steelhead Management Console Users Guidefor theSteelhead EX.



Overview of the Steelhead EX Granite Branch Storage

VSP Packages

To run on VSP, virtual machines are packaged as VSP services and uploaded to the Steelhead EX applianceand either stored in the library or installed in one of five slots.

A package can be:

a VM created by a third-party vendor that also contains configuration files specific to the Riverbed RSPimplementation.

a VM created by Riverbed.

a VM created internally within your organization. You can create packages using the Package Creatorwizard. For details, see the Steelhead Management Console Users Guidefor the Steelhead EX.

Users can configure installed services as follows:

Enable, disable, or restart.

Manage VM settings (priority, memory footprint, and such).

Manage ping or heartbeat watchdog settings.

Create, attach, and detach virtual disks.

Uninstall services from slots.

Note: VSP supports any packages that ran on the Riverbed Services Platform (RSP), which was available in RiOSversions before v7.0.

Virtual Network Interfaces (VNIs)

VSP packages communicate with the network through virtual network interfaces (VNIs). Connected to thephysical network interfaces on the Steelhead appliance, VNIs are network taps that enable data flow in and

out of the VSP packages. VNIs are the connection points for the LAN, WAN, primary, and auxiliaryinterfaces of the Steelhead appliance.

Each package can have up to ten VNIs, which provide the basis for controlling the flow of data throughpackages in a multiple-package scenario.

Granite Branch Storage

Granite is a dual-ended system that enables complete consolidation of storage at the data center, includingprivate clouds, by providing LAN performance for block-level access. This eliminates the need for

dedicated storage, including management and related backup resources, at the branch office.

Note: Granite functionality in Steelhead EX requires RiOS 7.0.2.

Granite does the following:

Provides LAN performance for block-level access at the branch office while consolidating storage atthe data center.



Granite Branch Storage Overview of the Steelhead EX

Improves performance for custom applications by eliminating the need for custom protocoloptimization.

Extends data-center class thin-provisioned storage to the branch office.

Allows extension of data-center deployed iSCSI SAN to all branch locations.

Eliminates need for storage management and backup resources at the branch office.

Provides infinite storage for branch services including virtualized branch services.

Simplifies disaster recovery strategy.

In brief, by consolidating all storage at the data center and creating diskless branches, Granite eliminatesdata sprawl, costly data replication, and the risk of data loss at the branch office.

For more information about Granite, see the Granite documentation including the Granite Core Installationand Configuration Guide.

How Granite Works

Granite enables edge server systems efficient access to storage arrays over the WAN. Granite is a dual-

ended system with Granite Core at the data center and a Granite-enabled Steelhead EX appliance at theedge.

The edge server connects to the Granite-enabled Steelhead EX appliance, which implements handlers forthe iSCSI protocol. The Granite-enabled Steelhead EX appliance also connects to the blockstore, a persistentlocal cache of storage blocks.

When the edge server requests blocks, those blocks are served locally from the blockstore. If they are notpresent, they are requested from the data center LUN (logical unit number). Similarly, newly written blocksare spooled to the local cache, acknowledged to the edge server, and then asynchronously propagated tothe data center. Because each Granite-enabled Steelhead EX appliance implementation is linked to adedicated LUN at the data center, the blockstore is authoritative for both reads and writes, and can tolerateWAN outages without worrying about cache coherency.

Blocks are communicated between Granite-enabled Steelhead EX appliances and Granite Core and the datacenter LUN via an internal protocol. (Optionally, this traffic can be further optimized by Steelheads forimproved performance.)

Granite initially populates the blockstore in several ways:

Reactive prefetch- The system observes block requests, applies heuristics based on these observationsto intelligently predict the blocks most likely to be requested in the near future, and requests thoseblocks from the data center LUN in advance.

Policy-based prefetch- Configured policies identify the set of blocks that are likely to be requested at agiven edge site in advance, and requests those blocks from the data center LUN in advance.

First request- Blocks are added to the blockstore when first requested. Because the first request iscold, it is subject to standard WAN latency.

System Architecture

At the data center, Granite Core integrates with existing storage systems and Riverbed implementations.Granite Core connects dedicated LUNs with each Granite-enabled Steelhead EX appliance at the edge orbranch office.



Overview of the Steelhead EX Granite-Dedicated Target Mode

Each Granite-enabled Steelhead EX appliance contains a blockstore that mirrors the datastore LUN. As aresult, the blockstore eliminates the need for separate block storage facilities at the branch office, as well asall the associated maintenance, tools, backup services, hardware, service resources, and such.

The following diagram illustrates a generic deployment.

Figure 1-2. Generic Granite Deployment

The basic system components are:

Microsoft Windows Edge Server- The branch-side server that accesses data from the Granite systeminstead of a local storage device.

Blockstore- The blockstore is a persistent local cache of storage blocks. Because each Granite-enabledSteelhead EX appliance is linked to a dedicated LUN at the data center, the blockstore is generallyauthoritative for both reads and writes.

In the above diagram, the blockstore on the branch side synchs with LUN1 at the data center.

iSCSI Initiator- The iSCSI initiator is the branch-side client that sends SCSI commands to the iSCSItarget at the data center.

Granite-enabled Steelhead EXappliance- The branch-side component of the Granite system links the

edge server to the blockstore and links the blockstore to the iSCSI target and LUN at the data center.The Steelhead provides general optimization services.

Data Center Steelhead- The data center-side Steelheadpeer for general optimization.

Granite Core- The data center component of the Granite system. Granite Core manages blocktransfers between the LUN and the Granite-enabled Steelhead EX appliance.

iSCSI Target- The data center-side server that communicates with the branch-side iSCSI initiator.

LUNs- Each Granite-enabled Steelhead EX appliance requires a dedicated LUN in the data centerstorage configuration.

Granite-Dedicated Target Mode

Granite-dedicated target mode refers to a Granite-enabled Steelhead EX appliance that provides neitherWAN optimization nor VSP functionality.

Appliances in Granite-dedicated target mode are intended to be used in conjunction with existing Steelheaddeployments, thereby enabling customers to take advantage of Granite functionality without upgradingtheir existing Steelhead appliances.



CHAPTER 2 Managing Riverbed Licenses

This chapter describes the Riverbed licensing methods and how to manage Riverbed licenses. It includesthe following sections:

Riverbed Licensing Methods, next

Automatic Licensing on page 20

Retrieving Licenses Using the Riverbed Licensing Portal on page 21

Riverbed Licensing Methods

A license is a string issued by Riverbed that embeds information that ties the license to data to preventtampering. After you install the license, the system saves it in the configuration database and enables thefunctionality associated with the license. Riverbed employs the following licensing methods:

Automatic Licensing- Once you connect your Steelhead appliance to the network, the Steelhead

appliance automatically contacts the Riverbed Licensing Portal which downloads and installs thelicenses. For detailed information, see Connecting to the Steelhead Appliance on page 32.

Manual Licensing- You can fetch and activate licenses for Riverbed products using the RiverbedLicensing Portal. Simply go to https://licensing.riverbed.com/index.htm and follow the instructionsto retrieve license keys.

Factory Licensing- You can have all your Riverbed licenses installed at the factory for a small fee.

Token Method- You use tokens to activate Riverbed software, such as the Virtual Steelhead Mobile,Virtual Whitewater, Virtual Steelhead, and HP ProCurve. For detailed information, see the respectiveinstallation guides for these products.



Managing Riverbed Licenses Automatic Licensing

Automatic Licensing

Automatic licensing allows the Steelhead appliance, once connected to the network, to automaticallycontact the Riverbed Licensing Portal to retrieve and install license keys for the appliance. Automaticlicensing 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 optionor by downloading and XML file to the Riverbed Central Management Console. For detailed information,see Retrieving Licenses Using the Riverbed Licensing Portal on page 21.

Tip: If automatic licensing fails an error message appears in the Management Console. Go to the Riverbed LicensingPortal and follow the instructions for retrieving your licenses.

To view licenses on a new Steelhead appliance

Connect the new Steelhead appliance to the network.

The Steelhead appliance automatically contacts the Riverbed Licensing Portal which downloads andinstalls the licenses. The Management Console Licensing page displays a success message or the AlarmStatus page reports an actionable error message.

To replace expired licenses

Purchase new downloadable licenses to replace the expired license.

At the time of the next scheduled automatic license fetch, the Steelhead appliance automaticallycontacts the Riverbed License Portal and downloads the new licenses. The Management ConsoleLicensing page displays a success message or the Alarm Status page reports an actionable errormessage.

To fetch a license on demand

1. In the Management Console, choose Configure > Maintenance > Licenses to display the Licenses page.

2. Click Fetch Updates Now.

The Management Console Licensing page displays a success message or the Alarm Status page reportsan actionable error message.

Note: Only administrator users can fetch and install licenses. For detailed information on administrator and monitorusers, see the Steelhead Management Console Users Guide.



Retrieving Licenses Using the Riverbed Licensing Portal Managing Riverbed Licenses

Retrieving Licenses Using the Riverbed Licensing Portal

You can retrieve and manage Riverbed licenses using the Riverbed Licensing Portal. The RiverbedLicensing Portal simplifies license management by providing an automated way to fetch and activatelicenses for Riverbed products.

To retrieve your licenses using the Riverbed Licensing Portal

1. Copy the barcoded Serial Number (SN) and Manufacturing Serial Number (MFG) that is located on thefront, back, or side of your appliance.

2. Go to the License Activation page in the Riverbed Licensing Portal at https://licensing.riverbed.com/index.htm

Figure 2-1. Riverbed Licensing Portal

3. To retrieve your licenses by serial number, type your name, email address, phone number, and SerialNumber (SN) and click Submitto display the Software License Summary page.

The serial numbers are on barcoded labels located on the front, back, or side of your appliance.



Managing Riverbed Licenses Retrieving Licenses Using the Riverbed Licensing Portal

4. For each serial number, click the check box for the software feature you want to activate and clickRefresh.

Make sure your serial numbers match the software features. You cannot make changes after you haveactivated selected licenses.

Figure 2-2.

5. Optionally, if you are behind a firewall, type the email address in the Email address text box and clickEmail Keysto have the license keys emailed to you.

6. Optionally, if you are behind a firewall, click Download XMLto download an XML file.

The Riverbed Central Management Console can import the XML file.

Tip: Click New Searchto search for additional license records.



Retrieving Licenses Using the Riverbed Licensing Portal Managing Riverbed Licenses

Installing Your License Keys

Each license key is generated for a specific appliance; make sure to install your license key on theappropriate appliance.

To install a license using the CLI

1. Connect to the CLI of the appliance and enter configuration mode.

For details see the Riverbed Command-Line Interface Reference Manual.

2. At the system prompt, enter the following commands:

license install write memory

To install a license using the Management Console

1. Connect to the Management Console of the appliance.

For details, see the Steelhead Management Console Users Guide.

2. Choose Configure > Maintenance > Licenses to display the Licenses Page.

3. In the Licenses Text Box, copy and paste the license key provided by Riverbed Licensing Portal into thetext box.

Separate multiple license keys with a space, Tab, or Enter.



Managing Riverbed Licenses Retrieving Licenses Using the Riverbed Licensing Portal



CHAPTER 3 Installing and Configuring theSteelhead Appliance

This chapter describes how to install and configure the Steelhead appliance. It includes the followingsections:

Choosing a Network Deployment, next

Checking Your Inventory on page 27

Preparing Your Site for Installation on page 28

Completing the Configuration Checklist on page 29

Powering On the Steelhead Appliance on page 31

Connecting to the Steelhead Appliance on page 32

Configuring In-Path Steelhead Appliances on page 33

Configuring Out-of-Path Steelhead Appliances on page 42

Important: 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.

Choosing a Network Deployment

Typically, the Steelhead appliance is deployed on a LAN, with communication between appliances takingplace over a private WAN or VPN. Because optimization between Steelhead appliances usually takes placeover a secure WAN, it is not necessary to configure company firewalls to support Steelhead-specific ports.

Note: If there are one or more firewalls between two Steelhead appliances, ports 7800 and 7810 must be passed throughfirewall devices located between the pair of Steelhead appliances. Also, SYN and SYN/ACK packets with the TCPoption 76 must be passed through firewalls for auto-discovery to function properly.

For optimal performance, you should minimize latency between Steelhead appliances and their respectiveclients and servers. Steelhead appliances should be as close as possible to your network end points (client-side Steelhead appliances should be as close to your clients as possible and server-side Steelhead appliancesshould be as close to your servers as possible).



Installing and Configuring the Steelhead Appliance Choosing a Network Deployment

Ideally, Steelhead appliances optimize only traffic that is initiated or terminated at their local site. The bestand easiest way to achieve this is to deploy the Steelhead appliances where the LAN connects to the WAN,and not where any LAN-to-LAN or WAN-to-WAN traffic can pass through (or be redirected to) theSteelhead appliance.

For detailed information about your deployment options and best practices for deploying Steelheadappliances, see the Steelhead Appliance Deployment Guide.

Before you begin the installation and configuration process, you must select a network deployment:

Physical In-Path- In a physical in-path deployment, the Steelhead appliance isphysicallyin the directpath between clients and servers. The clients and servers continue to see client and server InternetProtocol (IP) addresses. In-path designs are the simplest to configure and manage, and the mostcommon type of Steelhead appliance deployment, even for large sites.

Figure 3-1. Physical In-Path Deployment

Virtual In-Path- In a virtual in-path deployment, a redirection mechanism (such as WCCP, PBR, orLayer-4 switching) is used to place the Steelhead appliance virtually in the path between clients andservers.

Figure 3-2. Virtual In-Path: WCCP Deployment



Checking Your Inventory Installing and Configuring the Steelhead Appliance

Out-of-Path- In an out-of-path deployment, the server-side Steelhead appliance is not in the directpath between the client and the server. In an out-of-path deployment, the Steelhead appliance acts as aproxy. This type of deployment might be suitable for locations where physical in-path or virtual in-path configurations are not possible.

Figure 3-3. Out-of-Path Deployment

Checking Your Inventory

Your shipping carton contains the following items:

The Steelhead appliance

One standard Ethernet straight-through cable

One standard Ethernet crossover cable

One serial null-modem cable

One or two power cables (depending on your order)

Aside from country-specific requirements, all systems ship with the same power cable. The powercable has a IEC 60320 C13 plug on one end (to connect to the Steelhead appliance) and a country-specific plug that fits the wall socket for that country. If a system has two power supplies, it ships withtwo suitable cables.

You must always connect the Steelhead appliance using either the cable in the accessories box oranother cable that is approved for use by the IEC in the country in which the appliance is connected.

You cannot connect a Steelhead appliance directly to multiphase outlets. You must use a rack PDU orpower strip that provides the appropriate three-prong outlet (hot/neutral/ground). For details, see theKnowledge Base solution number S13425.

One Phillips screwdriver

Rails are preinstalled on the EX Series xx60 platforms.

One mounting kit

Documentation kit

If any items are damaged or missing, notify Riverbed Support at https://support.riverbed.com forreplacement or repair.
https://support.riverbed.com/kb/solution.htm?id=501700000008yIy&categoryName=Hardwarehttps://support.riverbed.com/kb/solution.htm?id=501700000008yIy&categoryName=Hardwarehttps://support.riverbed.com/kb/solution.htm?id=501700000008yIy&categoryName=Hardwarehttps://support.riverbed.com/kb/solution.htm?id=501700000008yIy&categoryName=Hardware



Installing and Configuring the Steelhead Appliance Preparing Your Site for Installation

Preparing Your Site for Installation

The Steelhead appliance ships completely assembled, with all the equipment parts in place and securelyfastened.

Before you install the Steelhead appliance, make sure that your site meets the following requirements: It is a standard electronic environment where the ambient temperature does not exceed 40 C (104 F)

and the relative humidity does not exceed 80% (noncondensing). For detailed information, see theappendix.

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 theSteelhead appliance to a rack, see the Rack Installation Guideor the printed instructions that wereshipped with the system.

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 Rack Installation Guidefor detailed information about how to install yourmodel to a rack.

Note: Riverbed recommends that you use a four-post mounting rack for 2U systems.

Note: If your rack requires special mounting screws, contact your rack manufacturer.



Completing the Configuration Checklist Installing and Configuring the Steelhead Appliance

Completing the Configuration Checklist

The following table lists the parameters you specify to complete the initial configuration of the Steelheadappliance. Be prepared to provide values for these parameters.

Appliance Parameter Your Value

Steelhead Appliance(thePrimary Interface)

Host name

IP address

Netmask

Default gateway (the WANgateway)

DNS IP address

Domain name for the system

Administrator password

SMTP server IP address

Events and failures notificationemail address

Primary interface speed

Primary interface duplex

In-Path Deployments In-path interface IP address

In-path netmask

In-path gateway

In-path: LAN interface speed

In-path: LAN interface duplex

In-path: WAN interface speed

In-path: WAN interface duplex



Installing and Configuring the Steelhead Appliance Completing the Configuration Checklist

Steelhead Appliance Ports

The following table summarizes the ports used to connect the Steelhead appliance to your network.

Bypass Card Interface Naming Conventions

The interface names for the bypass cards are a combination of the slot number and the port pairs

(_, _). For example, if a four-port bypass card is located in slot 0 of your appliance,the interface names are lan0_0, wan0_0, lan0_1, and wan0_1, respectively. Alternatively, if the bypass cardis located in slot 1 of your appliance, the interface names are lan1_0, wan1_0, lan1_1, and wan1_1,respectively.

For detail information about bypass cards on the EX560 and EX760, see the Series EX560 and EX760 SystemsOwners Manual.

For detailed information about installing additional bypass cards, see the Network Interface Card InstallationGuide.

Port Description

Console Connects the serial cable to a terminal device. You establish a serial connection to aterminal emulation program for console access to the configuration wizard and theSteelhead CLI.

Primary(PRI)

The management interface that connects the Steelhead appliance to a LAN switch. Thismanagement interface enables you to connect to the Management Console and theSteelhead CLI.

The primary and auxiliary ports cannot share the same network subnet.

The primary and in-path interfaces can share the same subnet.

You must use the primary port on the server-side for out-of-path deployments.

Auxiliary (AUX) An optional port that provides an additional management interface for a secondarynetwork. You cannot have the primary and auxiliary ports on the same subnet.

The auxiliary and in-path interfaces cannot share the same network subnet.

You cannot use the auxiliary port for out-of-path Steelhead appliances.

WAN Connects the WAN port of the Steelhead appliance and the WAN router using a crossovercable.

LAN Connects the LAN port of the Steelhead appliance and the LAN switch using a straight-through cable.

Note: If the Steelhead appliance is deployed between two switches, both the LAN andWAN ports must be connected with straight-through cables.



Powering On the Steelhead Appliance Installing and Configuring the Steelhead Appliance

Powering On the Steelhead Appliance

The following section describes how to connect the AC power and how to power on the system.

Caution: In European electrical environments, you must ground (earth) the Green/Yellow tab on the power cord or riskelectrical shock.

To power on the system

1. Ensure that the system power switch is in the off position on the rear of the Steelhead appliance.

2. Plug the AC power cord into the Steelhead appliance.

Note: If your model has multiple power supplies, you must plug in all the power cords or you will hear an alarm.

Figure 3-4. Connecting the AC Power

3. Plug the AC power cord into an uninterrupted AC power source.

4. Press the system power switch on.

If the Steelhead appliance does not immediately power on, press the power switch off, then press thepower switch on again.

5. Check the status lights on the Steelhead appliance.

For detailed information about the status lights, see the appendix.

Note: The 1U and 2U Steelhead EX appliances (Series xx60) takes 15 minutes to start. The EX555 and EX755 take about7 minutes to start.



Installing and Configuring the Steelhead Appliance Connecting to the Steelhead Appliance

Connecting to the Steelhead Appliance

To access the configuration wizard and the Steelhead CLI, you establish a serial connection using a terminalemulator program.

To connect to the Steelhead appliance

1. Plug the serial cable into the Serial/Console port and a terminal.

Do not use the VGA or DVI ports to connect to the appliance.

Figure 3-5. Connecting to the Steelhead Appliance

2. Start your terminal emulation program, such as Tera Term Pro. The terminal device must have thefollowing settings:

Baud rate: 9600 bps

Data bits: 8

Parity: none

Stop bits: 1

vt100 emulation

No flow control

Note: If you are using the Steelhead appliance with a terminal server, the terminal server must use hardware flowcontrol for the port connected to the Steelhead appliance.

Tip: Riverbed recommends that you connect the console port to a device that logs output. Even though this is not arequirement, it can help you identify problems with the system.

3. Log in as administrator user (admin) and enter the default password (password).

For example,

login as: adminSent username "admin"password: password

The configuration wizard automatically starts after you enter the login and default password.

After you have established a connection, you configure the Steelhead appliance using the configurationwizard:



Configuring In-Path Steelhead Appliances Installing and Configuring the Steelhead Appliance

For in-path configurations, see Configuring In-Path Steelhead Appliances, next.

For out-of-path configurations, see Configuring Out-of-Path Steelhead Appliances on page 42.

Configuring In-Path Steelhead AppliancesIn a physical in-path deployment, the Steelhead appliance is physically in the direct path between clientsand servers. The clients and servers continue to see client and server IP addresses. Physical in-pathconfigurations are suitable for any location where the total bandwidth is within the limits of the installedSteelhead appliance. For a detailed figure, see Choosing a Network Deployment on page 25.

For detailed information about in-path deployments, see the Steelhead Appliance Deployment Guide.

Avoiding Duplex Mismatch

Before you begin the configuration process, ensure that your LAN and WAN interfaces have the sameduplex settings.

The Steelhead appliance automatically negotiates duplex settings. If one end of the link is set to auto-negotiate and the other end of the link is not set to auto-negotiate, the duplex settings on the network devicedefault to half-duplex. This duplex mismatch passes traffic, but it causes late collisions and results indegraded optimization. To achieve maximum optimization, set your network devices to 100 and full.

To avoid duplex mismatches, manually configure the duplex settings on your:

router

switch

Steelhead appliance WAN interface

Steelhead appliance LAN interface

Steelhead appliance primary interface

The following can be signs of a duplex mismatch:

On the Reports > Diagnostics > System Logs page, you see errors for sends, receives, CRC, and shortsends.

You cannot connect to an attached device.

You can connect to a device when you choose auto-negotiation, but you cannot connect to that samedevice when you manually set the speed or duplex.

Slow performance across the network.

For detailed information about checking for duplex mismatches, see Chapter 4, Troubleshooting.

Configuration Wizard

The configuration wizard automatically starts when you log in to the CLI for the first time.

When using the configuration wizard:

Click Enterto enter the default value.

Click ?for help.



Installing and Configuring the Steelhead Appliance Configuring In-Path Steelhead Appliances

Click Ctrl-Bto go back to the previous step.

If you quit the configuration wizard, you can restart it from the Steelhead CLI. You must be in configurationmode to restart the configuration wizard.

To restart the configuration wizard

Enter the following set of commands at the system prompt:> enable# configure terminal(config) # configuration jump-start

For detailed information about the CLI, see the Riverbed Command-Line Interface Reference Manual.

To configure the Steelhead appliance in an in-path deployment

1. If you have a Riverbed Central Management Console (CMC) appliance installed in your network tomanage multiple Steelhead appliances, you can use it to automatically configure them:

Do you want to auto-configure using a CMC? no

If you answer yes, you are prompted for the CMC host name or IP address. The host name or IP

address is used to contact the CMC. The default value is riverbedcmc. If you enter no, the wizardcontinues.

Tip: If you mistakenly answer yes, to return to the wizard from the CLI, enter the configuration jump-startcommandfrom configuration mode. For detailed information, see the To restart the configuration wizard on page 34.

2. To start the configuration wizard, enter yesat the system prompt.

Do you want to use the configuration wizard for initial configuration? yes

3. Complete the configuration wizard steps on the client-side and the server-side Steelhead appliances asdescribed in the following table.

Wizard Prompt Description Example

Step 1: Host name? Enter the host name for the Steelheadappliance.

hostname? amnesiac

Step 2: Use DHCP on theprimary interface?

You are given the option to enable theDHCP to automatically assign an IPaddress to the primary interface forthe Steelhead appliance.

Riverbed recommends that you do notset DHCP.

The default value is no.

Use DHCP? no

Step 3: Primary IP address? Enter the IP address for the Steelheadappliance.

Primary IP address? 10.10.10.6

Step 4: Netmask? Enter the netmask address. Netmask? 255.255.0.0

Step 5: Default gateway? Enter the default gateway for theSteelhead appliance.

Default gateway? 10.0.0.1

Step 6: Primary DNS server? Enter the primary DNS server IPaddress.

Primary DNS server? 10.0.0.2




Step 7: Domain name? Enter the domain name for thenetwork where the Steelheadappliance is to reside.

If you set a domain name, you canenter host names in the systemwithout the domain name.

Domain name? example.com

Step 8: Admin password? Riverbed strongly recommends thatyou change the default administratorpassword at this time. The passwordmust be a minimum of six characters.

The default administrator password ispassword.

Admin password? xxxyyy

Step 9: SMTP server? Enter the name of the SMTP server.External DNS and external access forSMTP traffic is required for emailnotification of events and failures tofunction.

Important: Make sure that youprovide a valid SMTP server to ensurethat the email notifications for eventsand failures.

SMTP server? natoma

Step 10: Notification emailaddress?

Enter a valid email address to whichnotification of events and failures areto be sent.

Notification email [email protected]

Step 11: Set the primary interfacespeed?

Enter the speed on the primaryinterface (that is, the Steelheadappliance). Make sure that this valuematches the settings on your router orswitch.

The default value is auto.

Set the primary interface speed?[auto] auto

Step 12: Set the primary interfaceduplex?

Enter the duplex mode on the primaryinterface. Make sure that this valuematches the settings on your router orswitch. The default value is auto.

Set the primary interfaceduplex? [auto] auto

Step 13: Would you like toactivate the in-pathconfiguration?

Enter yesat the system prompt toconfigure in-path support. An in-pathconfiguration is a configuration inwhich the Steelhead appliance is inthe direct path of the client and server.

For detailed information about in-path configurations, see the Steelhead

Appliance Deployment Guide.

Would you like to activate thein-path configuration? yes

Step 14: In-Path IP address? Enter the in-path IP address for theSteelhead appliance.

In-Path IP address? 10.11.11.6

Step 15: In-Path Netmask? Enter the in-path netmask address. In-Path Netmask? 255.255.0.0

Step 16: In-Path Defaultgateway?

Enter the in-path default gateway (theWAN gateway).

In-Path Default Gateway?10.11.11.16




Installing and Configuring the Steelhead Appliance Configuring In-Path Steelhead Appliances

4. The system confirms your settings.

You have entered the following information:1. Hostname: amnesiac2. Use DHCP on primary interface: no

3. Primary IP address: 10.10.10.64. Netmask: 255.255.0.05. Default gateway: 10.0.0.1

6. Primary DNS server: 10.0.0.27. Domain name: example.com8. Admin password: xxxyyy

9. SMTP server: natoma

10. Notification email address: [email protected]. Set the primary interface speed: auto12. Set the primary interface duplex: auto13. Would you like to activate the in-path configuration: yes14. In-Path IP address: 10.11.11.615. In-Path Netmask: 255.255.0.016. In-Path Default gateway: 10.11.11.1617. Set the in-path:LAN interface speed: auto18. Set the in-path:LAN interface duplex: auto19. Set the in-path:WAN interface speed: auto20. Set the in-path:WAN interface duplex: autoTo change an answer, enter the step number to return to.Otherwise hit to save changes and exit.Choice:

The Steelhead appliance configuration wizard automatically saves your configuration settings.

5. To log out of the system, enter the following command at the system prompt:

amnesiac> exit

Step 17: Set the in-path: LANinterface speed?

Enter the in-path, LAN interfacespeed. Make sure that this valuematches the settings on your router orswitch.


Set the in-path: LAN interfacespeed? [auto] auto

Step 18: Set the in-path: LANinterface duplex?

Enter the in-path, LAN duplex value.Make sure that this value matches thesettings on your router or switch.


Set the in-path: LAN interfaceduplex? [auto] auto

Step 19: Set the in-path: WANinterface speed?

Enter the in-path, WAN interfacespeed. Make sure that this valuematches the settings on your router orswitch.


Set the in-path: WAN interfacespeed? [auto] auto

Step 20: Set the in-path: WANinterface duplex?

Enter the in-path, WAN duplex speed.Make sure that this value matches the

setting on your router or switch.The default value is auto.

Set the in-path: WAN interfaceduplex? [auto] auto





Connecting the Steelhead Appliance to Your Network

You use standard Ethernet straight-through and crossover cables to connect to your network in an in-pathconfiguration. Make sure that you use the correct cables to establish your network connections:

Straight-through cables- Primary and LAN ports on the applianc

Steelhead® Appliance Installation and Configuration Guide

Documents

Transcript of Steelhead® Appliance Installation and Configuration Guide