This chapter describes the process for installing the Stingray Services Controller Virtual Appliance (Services Controller VA). Upgrading and downgrading procedures for both the Services Controller VA and Instance Host VAs are also provided.
This chapter includes the following sections:
“Overview of the Services Controller VA” on page 156 “Prerequisites” on page 156
“Obtaining the Services Controller VA Software” on page 159
“Installing, Configuring, and Administering the Services Controller VA” on page 160 “Creating the VM in vSphere” on page 161
“Running the Services Controller VA Setup Wizard” on page 162 “Upgrading the Services Controller VA” on page 175
“Downgrading the Services Controller VA” on page 176 “Upgrading Instance Host VAs” on page 176
Note: This chapter assumes that you are familiar with installing, configuring, and managing virtual appliances or machines (VAs or VMS) using VMware® vSphere® Hypervisor (vSphere).
Installing the Services Controller Virtual Appliance Overview of the Services Controller VA
Overview of the Services Controller VA
The Services Controller VA enables you to install, configure, and manage the Services Controller as a virtual appliance. Rather than managing a Linux installation, the Services Controller VA provides a graphical user interface (GUI) and a command-line interface (CLI) that enables you to create and manage Service Controller instances. Finally, the Services Controller VA image also includes the MySQL database, simplifying the installation process.
After you create a VM in VMware vSphere, you use the Services Controller VA GUI to run an initial Setup wizard that populates the Services Controller VA with the necessary information for administering and managing the Services Controller.
After you have run the Setup wizard, you can use either the GUI or the CLI to manage:
certificates and private keys, licenses, and software images for the Services Controller and Traffic Manager.
instances, instance hosts, users, and clusters.
users credentials, feature packs, metering, and logging.
health and monitoring reports, system logs, and system dumps.
Prerequisites
Before you begin installing the Services Controller VA, you must make sure that you have the correct software, hardware, and configuration information.
Note: All required files must be in accessible locations in your infrastructure during the installation process. This will typically be on an accessible server, but can also be on your local machine.
To install the Services Controller VA, you need the following software and hardware:
OVAs - Two open virtual appliance (OVA) files are available:
– the Services Controller OVA. This is used to install the Services Controller VA. See “Creating the
VM in vSphere” on page 161.
– the Instance Host OVA. This is used inside the Services Controller VA after installation, and is not required for initial installation. “Creating and Managing Instance Hosts” on page 205.
You must place the OVA files in an accessible location in your infrastructure. You can obtain the OVAs from Riverbed Support at https://support.riverbed.com.
Services Controller Licenses - You must place the Services Controller Licenses (either CSP or Enterprise) and the Bandwidth Pack license key on an accessible location in your infrastructure. For details about retrieving your Services Controller licenses, see “To retrieve Stingray and Services
Controller product licenses” on page 18.
Traffic Manager Image - The Traffic Manager image (a tarball) is required to create Traffic Manager instances in the Services Controller. You must place the image file in a locally accessible directory on each Services Controller server in your infrastructure. You can download the Traffic Manager image
Stingray Services Controller User’s Guide 157
Prerequisites Installing the Services Controller Virtual Appliance
Traffic Manager FLA License - The Traffic Manager FLA license is required to create instances in the Services Controller VA. You must place the external file in a locally accessible directory on each Services Controller server in your infrastructure. For details about retrieving your Services Controller licenses, see “To retrieve Stingray and Services Controller product licenses” on page 18.
SSL Certificate/Key - The Traffic Manager FLA license requires that you generate a self-signed SSL certificate and key. You must place these files on an accessible location in your infrastructure.
VMware vSphere ESXi 5.0+ - The Services Controller VA runs on vSphere ESXi 5.0+. However, the ssc
host provision command to provision an instance host works only on ESXi 5.0 and 5.1, not ESXi 5.5. Riverbed assumes that you are familiar with creating and managing VMS using vSphere. For detailed information about creating virtual machines using vSphere, see http://www.vmware.com/products/.
MySQL Database - The MySQL database with a user account is required for the Services Controller VA. The MySQL database is automatically installed when you install the Services Controller VA.
SMTP Server - An SMTP server is required for Email alerts. The Services Controller VA does not support SMTP connections that require authentication.
Log and File Store - Accessible directories are required for logs and file storage.
Note: If you have not received your Services Controller, enterprise bandwidth, and Traffic Manager FLA licenses, contact Riverbed Licensing ([email protected]) for assistance.
Resource Requirements
The Services Controller VA requires the following resources for the virtual machine. You can deploy flavors (which are different sizes) of instance host VMs.
VA Type CPU Memory Disk
SSC VA 4 vCPU 8 GB 46 GB
Small Flavor Instance
Host VA 2 vCPU 4 GB 70 GB
Large Flavor Instance
Installing the Services Controller Virtual Appliance Prerequisites
Required Configuration Information
The Administration UI Setup wizard prompts you to provide information that is used to configure the Services Controller VA. Make sure that you have the following information before you start the Setup wizard.
Note: You can also use the configuration wizard in the CLI to configure the Services Controller VA. For detailed information about connecting to the Services Controller VA, see the Stingray Services Controller Command-Line Interface Reference Manual. The first time you log in the configuration wizard starts automatically. If you need to rerun the configuration wizard, use the configuration jump-start command.
Parameter Description
Hostname The hostname for the Services Controller.
Primary IP address The IP address for the Services Controller. DNS Server The IP address for the primary name server. IPv4 DHCP or IPv6 Settings for IPv4 or IPv6 traffic.
SMTP server and port The name of the SMTP server and port. External DNS and external access for SMTP traffic is required for email notification of events and failures to function. Email notification address A valid email address to which notification of events and failures are to be sent.
Note: You can also configure the "From" e-mail address of alert e-mails. This address can be set in INSTALLROOT/conf/email_config.txt, in the common section, as from_address. The symbol "$fqdn" will be replaced by the fully- qualified domain name of the SSC host. The other sections in this file should not normally be modified. For SSC installs on AWS it is likely that you will need to change this setting to be an address that is resolvable to the instance's public IP. SSL certification and private key Imports the self-signed Secure Socket Layer (SSL) SSL certificate and private
key file. For example, a local file, or an http, ftp, or scp URL.
scp://username:password@host/path/filename
Ensure these files are located on an accessible location in your infrastructure. Services Controller License and
Bandwidth Pack License Imports the Services Controller (CSP or Enterprise) license and Enterprise Bandwidth Pack license. Make sure these files are located on an accessible location in your infrastructure.
Traffic Manager (STM) FLA
license Imports the Traffic Manager FLA license. Make sure this file is located on an accessible location in your infrastructure. Administrator user and
password The administrator password for the Services Controller. This password is used to access the Services Controller CLI and UI. Riverbed strongly recommends that you change the default administrator password at this time. The password must be a minimum of six characters.
The default administrator user is admin and the password is password. Traffic Manager Image Imports the Traffic Manager image and creates a version resource. This
resource is necessary to create an instance. Make sure the Traffic Manager image file is located on an accessible location in your infrastructure.
Instance Host OVA Uploads the Instance Host OVA file and creates an instance host. Make sure this file is located on an accessible location in your infrastructure.
Stingray Services Controller User’s Guide 159
Obtaining the Services Controller VA Software Installing the Services Controller Virtual Appliance
Obtaining the Services Controller VA Software
The Services Controller VA is provided by Riverbed Support as software that contains the VMX and VMDK files necessary to create virtual resources. Two OVAs are required:
Services Controller OVA - Creates a Services Controller virtual appliance on ESXi.
Instance Host OVA - Creates a virtual instance host on ESXi.
You obtain the Services Controller OVA and the Instance Host OVA from Riverbed Support at https:// support.riverbed.com.
Installing the Services Controller Virtual Appliance Installing, Configuring, and Administering the Services Controller VA
Installing, Configuring, and Administering the Services
Controller VA
You perform the following steps to install, configure, and manage resources in the Services Controller VA.
1. Generate a self-signed SSL certificate and private key for the Services Controller VA. Place these resources in your infrastructure on an accessible location.
2. Obtain the required OVA files (that is, the Services Controller OVA and the Instance Host OVA) from Riverbed Support. Place these resources in an accessible location in your infrastructure. For details about obtaining your license keys, see “To retrieve Stingray and Services Controller product licenses” on page 18.
3. Obtain the Services Controller licenses and the Enterprise Bandwidth Pack license from your Riverbed account team. Place these resources in your infrastructure on an accessible location. For details about obtaining your license keys, see “To retrieve Stingray and Services Controller product licenses” on page 18.
4. Obtain the Traffic Manager image and the FLA license from your Riverbed account team. Place these resources in your infrastructure on an accessible location. For details about obtaining your license keys,
see “To retrieve Stingray and Services Controller product licenses” on page 18.
5. Install the Services Controller OVA and the Instance Host OVA on vSphere and create a Services Controller VA. Make a note of the IP address to place in the browser window.
6. Power on the Services Controller VA in vSphere and log in to the Services Controller VA via any browser using the default username (admin) and password (password).
7. You must now run the Administration UI Setup wizard. Before you start, ensure that you have the prerequisite information. For details, see “Required Configuration Information” on page 158. The Setup wizard configures basic network settings, such as hostname, base interface settings, and email notifications. It also imports required licenses and certificates, and it creates an instance host. For details, see “Running the Services Controller VA Setup Wizard” on page 162.
You can also use the configuration wizard in the CLI to configure the Services Controller VA. For detailed information about connecting to the Services Controller VA, see the Stingray Services Controller
Command-Line Interface Reference Manual.
8. Change the password for the admin user via the CLI. See “Changing the Password for the Admin User”
on page 175.
9. You must enable passwordless SSH communication between the Services Controller and all instance hosts. See “Enabling Passwordless SSH Communication” on page 240.
10. Create instances (with or without LXC containers). For details, see “Configuring a Traffic Manager
Instance with a Container” on page 245 and “Creating a Traffic Manager Instance Without a Container”
on page 243.
11. Monitor the system and create system logs. For details, see “Viewing Logs and Generating System
Stingray Services Controller User’s Guide 161
Creating the VM in vSphere Installing the Services Controller Virtual Appliance
Creating the VM in vSphere
This section describes the procedures for installing the Services Controller VA OVA package on a VMware ESXi host using the vSphere client.
Note: This chapter assumes that you are familiar with installing, configuring, and managing VMs using VMware vSphere. The following instructions might vary. For detailed information about creating a VM in vSphere, see http:// www.vmware.com/products/vsphere-hypervisor/.
To create a VM in vSphere
1. Obtain the Services Controller OVA package from
https://support.riverbed.com and download it to a local machine.
2. Open vSphere, type the hostname IP address or name, type your username and password, and click
Login.
3. Choose File > Deploy OVF template.
4. Select Deploy from file, click Browse, and select the OVA file.
5. Click Open and Next.
6. Verify that the OVA file is the one you want to deploy and click Next.
7. Specify a name for the VM and click Next.
8. Select a host datastore in which to store the VM and its virtual disk files and click Next. Make sure that the host datastore you select has enough capacity for the OVA package to install. For example, for the SSC VM you need four CPUs, 8 GB of memory, and at least 46 GB of disk space.
9. On the Disk Format page, select Thick provisioned format and click Next. Thick provisioning preallocates all storage.
10. Select the destination network name, select a network from the drop-down list to map the source network to a destination network, and click Next.
11. Verify the deployment settings, and click Finish.
12. When the deployment finishes, click Close. The new VM appears under the hostname or host IP address of the VM inventory.
Installing the Services Controller Virtual Appliance Running the Services Controller VA Setup Wizard
Running the Services Controller VA Setup Wizard
After you have created the VM in vSphere, you complete the configuration process for the Services Controller VA using the Administration UI Setup wizard. The Setup wizard automatically starts the first time you log in to the Services Controller VA via a browser.
Riverbed recommends you use the Administration UI Setup wizard to configure the Services Controller VA rather than the CLI configuration wizard. The Administration UI Setup wizard enables you to perform the initial configuration for required licenses and certificates, and creates and provisions an instance host. Note: You can restart the Setup wizard at any time by selecting Manage > System Settings: Setup Wizard.
Note: You can also use the configuration wizard in the CLI to configure the Services Controller VA. For detailed information about connecting to the Services Controller VA, see the Stingray Services Controller Command-Line Interface Reference Manual. The first time you log in, the configuration wizard starts automatically. If you need to rerun the configuration wizard, use the configuration jump-start command.
To run the Setup wizard
1. Right-click the VM you created in vSphere and select Power and Power On.
2. In the vSphere Client UI, click the Services Controller VA that you created.
3. On the right side, click Summary in the panel and view the IP Addresses attribute. This attribute is the IP address for your Services Controller VA Administration UI. You might need to wait for a moment to allow the VM to fully start after the VM is powered on.
4. To connect to Services Controller VA Administration UI for the first time, place the IP address for your Services Controller VA in a browser window.
5. Log in using the default value for the administrator user (admin) and the default password (password), and click Log In.
Stingray Services Controller User’s Guide 163
Running the Services Controller VA Setup Wizard Installing the Services Controller Virtual Appliance
6. To start the Setup wizard, click Launch Setup Wizard.
Figure 8-2. Launch Setup Wizard Page
7. To configure the hostname, DNS settings, and Web proxy services, click Host Name to display the Hostname page.
Figure 8-3. Hostname Page
8. Complete the configuration as described in this table
.
Control Description
Hostname Specify the hostname for the Services Controller. Primary DNS Server Specify the IP address for the primary name server.
Secondary DNS Server Optionally, specify the IP address for the secondary name server. Tertiary DNS Server Optionally, specify the IP address for the tertiary name server. DNS Domain List Specify an ordered list of domain names.
If you specify domains, the system automatically finds the appropriate domain for each of the hosts that you specify in the system.
Installing the Services Controller Virtual Appliance Running the Services Controller VA Setup Wizard
9. To configure base interfaces, click Interface Configuration to display the Interface Configuration page.
Figure 8-4. Interface Configuration Page
10. Select the Enable Primary Interface check box and complete the configuration as described below. Note: Your browser will lose connection if you change the IP address of the primary interface. Close the browser and open the Services Controller VA using the new IP address after the configuration is applied.
11. Select the Enable Aux Interface check box if required and then complete the IPv4 configuration.
12. Configure the main IPv4 routing table. To do this, click the plus sign (+) above the Main IPv4 Routing Control Description
IPv4 DHCP Select this radio button to send the hostname with the DHCP request for registration with Dynamic DNS. Specify these settings:
• Dynamic DNS - Select this check box to automatically obtain the IP address from a DHCP server. A DHCP server must be available so that the system can request the IP address from it. • Address - Specify the IP address.
• Subnet - Specify the subnet address.
IPv4 Static Select this radio button if you do not use a DHCP server to set the IPv4 address. Specify these settings:
• Address - Specify an IP address. • Prefix - Specify a subnet mask.
Stingray Services Controller User’s Guide 165
Running the Services Controller VA Setup Wizard Installing the Services Controller Virtual Appliance
13. Complete the configuration as described in this table.
14. To set the configure the email settings, DNS settings, and Web proxy services, click Email Settings to display the Email Settings page.
Figure 8-5. Email Setting Page
15. Complete the configuration as described in this table.
Control Description
Destination IPv4 Address Specify the destination IP address. IPv4 Subnet Mask Specify a subnet mask.
Gateway IPv6 Address Specify the default gateway IPv4 address. The default gateway must be in the same network as the primary interface. You must set the default gateway for in- path configurations.
Interface Specify the interface type: Auto, primary, or aux.
Apply Click Apply to apply your changes to the running configuration.
Control Description
SMTP Server Specify the SMTP server. You must have external DNS and external access for SMTP traffic for this feature to function.
Note: Make sure you provide a valid SMTP server to ensure that the users you specify receive email notifications for events and failures.
SMTP Port Specify the port number for the SMTP server. Typically you do not need to change the