Pass the Riverbed RCSA-W 101-01 Questions and answers with CertsForce

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 <all> 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

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

https://support.riverbed.com/bin/support/download?did=oksf8h0os0pck6pv42smvag77t &version=9.2.1

Location awareness enables SteelHead Mobile to detect that it is in a branch office with a SteelHead, and it enables the SteelHead to optimize SteelHead Mobile traffic.

Configuring Endpoint Settings for Policies

You configure endpoint settings for SteelHead Mobile clients on the Endpoint Settings tab of the Manage > Policies page.

Note: A policy is a set of optimization, security, location awareness, storage, and other configuration settings that determine the optimization rules for the SteelHead Mobile clients. SteelHead Mobile clients must have a policy and other endpoint-specific settings for optimization.

References:

SteelCentral Controller for SteelHead, Mobile User’s Guide, Version 4.8, April 2016, page 143

https://support.riverbed.com/bin/support/download?did=ponkltmr1vg9mv23ok2fmtgkj4

The traffic for RiOS data store synchronization is transferred through either the Steelhead appliance primary or auxiliary network interfaces, not the in-path interfaces.

References:

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

https://support.riverbed.com/bin/support/download?did=a53locljdv9s5oc0agjp851iol

References:

SteelHead Deployment Guide Including the SteelCentral Controller for SteelHead Mobile, May 2016, page 174

https://support.riverbed.com/bin/support/download?did=7cmsbro2vbhvm7mn70uefgprbv

Generally, you select a SteelHead model based on the number of users, the bandwidth requirements, and the applications used at the deployment site. e. However:

If you want to optimize applications that transfer large amounts of data, choose your SteelHead model based on the amount of bandwidth, the number of concurrent connections at your site, and the size of the RiOS data store.

If you do not want to optimize applications that transfer large amounts of data (for example, WANbased backup or restore operations, system image, or update distribution), choose your SteelHead model based on the amount of bandwidth and number of concurrent connections at your site.

If you want to use SteelHead to enforce network Quality of Service (QoS), make sure to consider the SteelHead model QoS bandwidth in addition to the optimization criteria you need.

References:

SteelHead Deployment Guide Including the SteelCentral Controller for SteelHead Mobile, December 2014 (page 16)

https://support.riverbed.com/bin/support/download?did=hcsksjojd701t4t8v5s5qomoj7