Riverbed 101-01 Riverbed Certified Solutions Associate Exam Practice Test

A: OOP configuration does not support auto-discovery. You must create a fixed-target rule on the clientside Steelhead.

C: An out-of-path deployment is generally located on the server-side and is often described as a server-side outof-path deployment.

In an out-of-path deployment, only a SteelHead primary interface is required to connect to the network. The SteelHead can be connected anywhere in the LAN. An out-of-path SteelHead deployment does not have a redirecting device. You configure fixed-target in-path rules for the client-side SteelHead. The fixed-target in-path rules point to the primary IP address of the out-of-path SteelHead. The out-of-path SteelHead uses its primary IP address when communicating to the server. The remote SteelHead must be deployed either in a physical or virtual in-path mode.

Configure the Steelhead appliance to optimize Secure Windows traffic

Configuration steps for Signed SMB and Signed SMB2

3.2.1 On the server-side Steelhead navigate to Configure > Optimization > CIFS (SMB1).

3.2.2 Under the SMB Signing section, check the ‘Enable SMB Signing’ checkbox

3.2.3 Ensure the ‘NTLM Transparent Mode” option is selected

References:

Optimization in a Secure Windows Environment, White Paper , pages 35-36

References:

References:

To configure the remote management port

• Physically connect the REMOTE port to the network. You cable the remote management port to the Ethernet network in the same manner as the Primary interface.
• * Install the IPMItool on the client machine.
• * Assuming the IP address is 192.168.100.100, the netmask is 255.255.255.0, and the default gateway is 192.168.100.1, assign an IP address to the remote management port.

References:

Stingray Services Controller Command-Line Interface Reference Manual, Version 2.0, December 2014, page 201

The Riverbed SSL solution optimizes data transfers that are encrypted using SSL, provided that SteelHeads are deployed locally to both the client-side and server-side of the network.

Note: Secure Peering Using the Self-Signed Peer White, Gray, and Black Lists

You can use peering lists to configure peer certificates on SteelHeads running RiOS 5.0 or later. When SSL optimization is enabled, and an optimizable SSL connection is attempted across the SteelHeads, the remote peer is detected and its peering certificate is automatically populated into the self-signed peer gray list. The connection remains unoptimized because the remote peer is listed in the self-signed peer gray list.

You can examine the peer certificate for authenticity and move any peer from the gray list to either the white list or the black list. If you trust the remote peer, move it into the self-signed peer white list to begin optimizing the SSL connection. If you do not trust the remote peer, move it into the self-signed peer black list to prevent the SSL connection from being optimized.

References:

References:

RiOS has provided CIFS optimization since version 1.0, with ongoing enhancements in each subsequent version. CIFS optimization focuses on reducing the impact of WAN round-trip latency of common application and system behavior, including the Microsoft Office product suite, general file access, and remote printing.

References:

The SteelCentral Controller (SCC) supports monitoring only for SteelFusion Core 4.0 and later.

SCC 9.2 supports configuration and monitoring for SteelHead CX 8.6 and later.

SCC supports monitoring and partial configuration for SteelFusion Edge 4.0 and later.

SCC 9.2 supports configuration and monitoring for SteelHead EX 3.0 and later.

SCC 9.2 supports monitoring only for SteelHead Mobile 4.0 and later.

SCC 9.2 supports configuration and monitoring for SteelHead Interceptor 3.x and later.

References:

SteelCentral Controller for SteelHead User’s Guide, Version 9.2, May 2016, page 19

&version=9.2.1

To configure an HTTP optimization scheme for a particular hostname or server subnet

Choose Configure > Optimization > HTTP to display the HTTP page

Enabling the Enable HTTP Stream Splitting feature on the client-side Steelhead appliance to split Silverlight smooth streaming, Adobe Flash HTTP dynamic streams, and Apple HTTP Live Streaming (HLS).

This feature includes support for Microsoft Silverlight video and Silverlight extensions support on Information Internet Server (IIS) version 7.5 installed on Windows Server 2008 R2.

References:

Steelhead Appliance Management Console User’s Guide, Version 8.5.1, November 2013, pages 148, 150

&did=b0k7v640ooladbjgbjpt57rcb9

In All mode the SteelHead collects mappings for destination and source IP, destination and source MAC, VLAN tag, and Steelhead appliance inner connection traffic and auto-discovery options. This option has the advantage of learning simplified entries faster than the destination only option. Riverbed recommends that you use in topologies when you deploy the Steelhead appliance a 802.1q trunk.

In Destination and source mode the SteelHead collects mappings from destination and source IP, destination and source MAC, and VLAN tag (when deployed on 802.1q trunk).

In Destination only mode the SteelHead collects mappings from destination IP, destination MAC, and VLAN tag (when deployed

on 802.1q trunk).

References:

Steelhead Appliance Deployment Guide, Including the Steelhead Mobile Controller, December 2013, page 194