This chapter describes how to install and configure the Mobile Controller-v for  Virtual Services Platform (VSP). It includes the following sections:

This guide assumes that you are familiar with installing, configuring, and managing networks with deployed SteelHeads. For detailed information about the SteelHead and VSP, see the SteelHead Installation and Configuration Guide, the SteelHead EX Management Console User’s Guide, and the SteelHead Deployment Guide.

The Mobile Controller-v for VSP is a virtualized edition of the Mobile Controller appliance running on the VSP platform of a SteelHead EX. You can use the Mobile Controller-v for VSP to manage Mobile Controller licenses and control the deployment, management, and reporting of SteelHead Mobile clients. The Mobile Controller-v for VSP has the same functionality and performance as the Mobile Controller appliance except that it supports fewer licensed endpoints.

In SteelHead Mobile clients, VSP offers branch-office-in-a-box services. Mobile Controller-v for VSP requires VSP running on a SteelHead EX. The procedure for setting up Mobile Controller-v for VSP is different for EX 1.0, as described in Installing Virtual Mobile Controller in VSP for EX 1.0 and Installing Virtual Mobile Controller in VSP for EX 2.0 and Later.

Mobile Controller-v is not compatible with Riverbed Services Platform (RSP).

Mobile Controller-v for VSP requires at least 3 GB of RAM, at least 20 GB of available storage, and one 1 GHz CPU. If you do not allocate sufficient memory and CPU resources, you trigger the Virtual Machine Configuration alarm Raise Alarm When Virtual Machine is Detected to be Underprovisioned. This alarm displays a specific message for each underprovisioned resource.

For example, you might receive the following alarm message:

For VSP with SteelHead EX 1.0, you can set the Memory Footprint for each slot on the VSP Slots page. Do not change the default disk size set in the Mobile Controller-v for VSP package. Extending the disk size invalidates your licenses.

For VSP with SteelHead EX 2.0, you can configure the memory settings in vSphere or vCenter.

For detailed information about Mobile Controller alarms, see the SteelCentral Controller for SteelHead Mobile User’s Guide. For detailed information about setting Memory Footprint, see the SteelHead EX Management Console User’s Guide.

This section describes the prerequisites and the basic steps required to install the VSP installation image using the SteelHead Management Console. The section contains two parts. The first section describes the steps for setting up the Mobile Controller-v on a SteelHead EX 1.0, and the second section describes the steps for setting up the Mobile Controller-v on a a SteelHead EX 2.0 and later:

You add a VSP package in the SteelHead Management Console Configure > Branch Services > VSP Packages page. Use the Add a Package menu to upload a Mobile Controller-v for VSP package and then install it in a slot.

A VSP package contains the service or applications in a virtual machine and VSP-specific configuration files. A VSP package also contains RiOS configuration files, including the package virtual machine network interfaces (VNI). A VSP package includes a .vmx (virtual machine configuration) file and one or more .vmdk (virtual machine disk) files. You do not need to open or modify any of the files in the package. The package files can be quite large, and can sometimes take up several gigabytes of disk space.

You can install only one Mobile Controller-v for VSP on a SteelHead. The Mobile Controller-v for VSP package must be named RiverbedSMC.pkg. The name of the slot must be the same as the name of the package, without the extension. Since your package has the name RiverbedSMC.pkg, your slot must have the name RiverbedSMC.

For detailed information about VSP in SteelHead EX 1.0, including how to create a package and system requirements, see the 1.0 version of the SteelHead EX Management Console User’s Guide.

When you install a VSP package, you must select a VSP slot. A slot is a directory on disk. When you install a package into a slot, the system unpacks the VM into the directory. When you remove a package, the system deletes the files from the slot.

For more information about fetching packages, see the 1.0 version of the SteelHead EX Management Console User’s Guide.

You can install one package per slot. By default, the VSP slots are numbered 1 to 5. You must rename the slot you plan to use for Mobile Controller-v for VSP to RiverbedSMC.

In SteelHead EX 2.0 and later, you no longer install a VSP package in a slot on the appliance. Instead, you set up VSP for ESXi on the SteelHead EX and install the VSP image as described in Installing Mobile Controller-v for ESXi.

For detailed information about VSP in SteelHead EX 2.0 and later, including system requirements, see the corresponding version of the SteelHead EX Management Console User’s Guide: SteelHead EX (xx60), Chapter 3, “Working with the Virtual Services Platform.”

If you are running Mobile Controller-v on a SteelHead EX 1.0 appliance and want to upgrade to a SteelHead EX 2.0 appliance, you can migrate your Mobile Controller-v installation from 1.0 to 2.0. See version 2.0 of the SteelHead EX Management Console User’s Guide: SteelHead EX (xx60).

This section describes how to open a virtual machine (VM) console for a VSP package using either the command-line interface or the Mobile Controller Console.

After installing a VSP package, you can open the VM console client for the package from the VSP Slots page.

After installing a VSP package, you can open a VM console for the package using the SteelHead CLI.

For Mobile Controller-v for VSP with SteelHead EX 2.0 and later, use the procedure described for ESXi in Mobile Controller-v for ESXi Initial Configuration.

You log in to the Management Console on the Mobile Controller-v for VSP just as you would log in to the Mobile Controller Console on a Mobile Controller appliance. For instructions on logging in to the Mobile Controller Console, see Logging In to the Management Console.

Before you can add licenses to a Mobile Controller-v for VSP, you must purchase a token from Riverbed. The token has a model number assigned to the new Mobile Controller-v after you complete its licensing. To view your purchased token, log in to your account at the following site:

After you receive a token, you are ready to install the licenses.