About the SCC-v
This chapter provides an overview of the SCC-v: a virtualized appliance of the SteelCentral Controller for SteelHead specifically designed for customers (such as Managed Service Providers) and users who need to centrally manage multiple, separate deployments of the Riverbed system on behalf of their customers.
Product licensing
All licensing must be properly in place. Appliances can still be managed if appliance licenses are valid and available.
You need to have valid licenses installed on all appliances that you want to manage with the SCC-v.
A missing base license on an appliance can cause the health of the SCC-v to become critical and temporarily invalidates other SCC-v licenses, which in turn prevents management of appliances.
Networking requirements
You can access each SCC-v instance through HTTP, HTTPS, or SSH. You can configure the default access protocol in the Management Console. For details, see the SteelCentral Controller for SteelHead User Guide.
For SteelHead management, each SCC-v instance requires port 80 and port 443 inbound from the SteelHeads and port 22 outbound from each SCC-v instance to SteelHeads.
Hardware requirements for VMware infrastructure client
The installation process requires accessing the VMware Infrastructure Client (VIC) on a Windows workstation. For requirements, see the VMware documentation.
Hardware requirements per SCC-v instance
The SCC-v consists of three files:
• Hard disk 1 contains the operating system.
• Hard disk 2 is for statistics storage and must be provisioned according to the following table.
• Hard disk 3 is for RSP image and package management and must be provisioned based on total size of the image and package files.
Use the 64-bit SCC-v when managing more than 100 appliances.
The total datastore space required is the sum of the three VMDK files with a minimum value of 32 GB to a maximum of over 400 GB.
Number of appliances managed | Hard disk 2 | RAM | CPU (effective) |
Up to 50 | 50 GB | 4 GB | 2 core, 2 GHz |
Up to 100 | 100 GB | 6 GB | 2 cores, 2 GHz |
Up to 250* | 250 GB | 6 GB | 2 cores, 2 GHz |
Up to 500* | 400 GB | 16 GB | 4 cores, 2.4 GHz |
Up to 1500* | 400 GB | 32 GB | 4 cores, 4 GHz |
* Use the 64-bit product when managing more than 100 appliances.
Overview of the SCC-v
The SCC-v facilitates these administrative tasks as a multitenant solution for managing deployments of the Riverbed system across parallel network environments.
• Multiple Instances—The SCC-v is a virtual appliance that’s installed on a virtual machine. You can run multiple SCC-v instances, provided that the platform has sufficient hardware resources and the appropriate licenses are available.
• Configuration—The SCC-v enables you to automatically configure new SteelHead groups or to send configuration settings to appliances in remote offices. The SCC-v uses configuration objects (that is, policies and groups) to facilitate centralized configuration and reporting.
• Monitoring—The SCC-v provides both high-level status of and detailed statistics about the performance of SteelHeads and enables you to configure event notification for managed SteelHeads.
• Management—The SCC-v enables you to start, stop, restart, and reboot remote SteelHeads. You can also schedule jobs to send software upgrades and configuration changes to remote appliances or to collect logs from remote SteelHeads.
• Partial Federation —You can put any appliance into branch-managed mode to prevent configuration changes or maintenance operations from the SCC-v. The SCC-v continues to monitor and gather statistics from appliances that are branch managed.
• Operations History—The Operations History page in the Management Console lists all of the actions related to configuring SteelHeads that have been performed and indicates whether they were successful or not.