SteelFusion Core Installation and Configuration

SteelFusion Core Installation and Configuration
SteelFusion™ Core Installation and
Configuration Guide
Version 4.3
March 2016
© 2016 Riverbed Technology, Inc. All rights reserved.
Riverbed and any Riverbed product or service name or logo used herein are trademarks of Riverbed. All other trademarks used
herein belong to their respective owners. The trademarks and logos displayed herein cannot be used without the prior written
consent of Riverbed or their respective owners.
Akamai® and the Akamai wave logo are registered trademarks of Akamai Technologies, Inc. SureRoute is a service mark of
Akamai. Apple and Mac are registered trademarks of Apple, Incorporated in the United States and in other countries. Cisco is a
registered trademark of Cisco Systems, Inc. and its affiliates in the United States and in other countries. EMC, Symmetrix, and
SRDF are registered trademarks of EMC Corporation and its affiliates in the United States and in other countries. IBM, iSeries, and
AS/400 are registered trademarks of IBM Corporation and its affiliates in the United States and in other countries. Juniper
Networks and Junos are registered trademarks of Juniper Networks, Incorporated in the United States and other countries. Linux
is a trademark of Linus Torvalds in the United States and in other countries. Microsoft, Windows, Vista, Outlook, and Internet
Explorer are trademarks or registered trademarks of Microsoft Corporation in the United States and in other countries. Oracle and
JInitiator are trademarks or registered trademarks of Oracle Corporation in the United States and in other countries. UNIX is a
registered trademark in the United States and in other countries, exclusively licensed through X/Open Company, Ltd. VMware,
ESX, ESXi are trademarks or registered trademarks of VMware, Inc. in the United States and in other countries.
This product includes Windows Azure Linux Agent developed by the Microsoft Corporation (http://www.microsoft.com/).
Copyright 2012 Microsoft Corporation.
This product includes software developed by the University of California, Berkeley (and its contributors), EMC, and Comtech
AHA Corporation. This product is derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm.
The SteelHead Mobile Controller (virtual edition) includes VMware Tools. Portions Copyright © 1998-2013 VMware, Inc. All
Rights Reserved.
NetApp Manageability Software Development Kit (NM SDK), including any third-party software available for review with such
SDK which can be found at http://communities.netapp.com/docs/DOC-1152, and are included in a NOTICES file included
within the downloaded files.
For a list of open source software (including libraries) used in the development of this software along with associated copyright
and license agreements, see the Riverbed Support site at https//support.riverbed.com.
This documentation is furnished “AS IS” and is subject to change without notice and should not be construed as a commitment
by Riverbed. This documentation may not be copied, modified or distributed without the express authorization of Riverbed and
may be used only in connection with Riverbed products and services. Use, duplication, reproduction, release, modification,
disclosure or transfer of this documentation is restricted in accordance with the Federal Acquisition Regulations as applied to
civilian agencies and the Defense Federal Acquisition Regulation Supplement as applied to military agencies. This documentation
qualifies as “commercial computer software documentation” and any use by the government shall be governed solely by these
terms. All other use is prohibited. Riverbed assumes no responsibility or liability for any errors or inaccuracies that may appear
in this documentation.
Riverbed Technology
680 Folsom Street
San Francisco, CA 94107
Phone: 415-247-8800
Fax: 415-247-8801
Web: http://www.riverbed.com
Part Number
712-00076-09
Contents
Preface......................................................................................................................................................... 7
About This Guide ..........................................................................................................................................7
Audience ..................................................................................................................................................8
Document Conventions .........................................................................................................................8
Documentation and Release Notes ......................................................................................................8
Safety Guidelines ...........................................................................................................................................8
Contacting Riverbed......................................................................................................................................9
Chapter 1 - Overview of SteelFusion Core ............................................................................................. 11
Introducing SteelFusion..............................................................................................................................11
How SteelFusion Works..............................................................................................................................12
New Features in Core 4.3............................................................................................................................14
Product Dependencies and Compatibility ...............................................................................................14
Hardware and Software Dependencies.............................................................................................14
Core-v RAM and CPU Requirements................................................................................................15
Firewall Requirements .........................................................................................................................15
SNMP-Based Management Compatibility........................................................................................15
Ethernet Network Compatibility .......................................................................................................15
iSCSI-Compliant Storage Array Interoperability.............................................................................16
Upgrading the Core Software ....................................................................................................................17
Upgrading the Core Software Version...............................................................................................17
Downgrading the Core Software Version .........................................................................................19
Using the Riverbed Host Tools Installer............................................................................................19
Replacing a Core Appliance .......................................................................................................................20
Basic Steps..............................................................................................................................................20
Chapter 2 - Managing Riverbed Licenses ..............................................................................................25
Riverbed Licensing Methods .....................................................................................................................25
Automatic Licensing ...................................................................................................................................26
Manual and Token Licensing .....................................................................................................................27
SteelFusion Core Installation and Configuration Guide
3
Contents
Retrieving Licenses Using the Riverbed Licensing Portal..............................................................27
Installing Your License Keys ...............................................................................................................28
Chapter 3 - Configuring SteelFusion Core .............................................................................................29
Choosing a Network Deployment ............................................................................................................30
Checking Your Inventory............................................................................................................................30
Preparing Your Site for Installation...........................................................................................................31
Core Ports ..............................................................................................................................................31
NIC Interface Naming Conventions ..................................................................................................32
Powering On the Core.................................................................................................................................33
Configuring the Core ..................................................................................................................................34
Configuration Wizard ..........................................................................................................................34
Connecting Core to Your Network ....................................................................................................36
Connecting to the SteelFusion Core Management Console ...........................................................37
Viewing Version Information.....................................................................................................................38
Configuring the Core with Edges..............................................................................................................38
Prerequisites ..........................................................................................................................................38
Configuring the Edge...........................................................................................................................39
Configuring Storage .............................................................................................................................40
Configuring the Core ...........................................................................................................................40
Performing Additional Configuration Settings ...............................................................................49
Chapter 4 - Installing Core-v....................................................................................................................51
Overview of Core-v .....................................................................................................................................51
Hardware and Software Requirements ....................................................................................................52
Hardware Requirements .....................................................................................................................52
Recommendations for Optimal Performance...................................................................................52
Installing and Configuring Core-v for ESX..............................................................................................53
Obtaining the Core-v VM Image ...............................................................................................................54
Gathering Information ................................................................................................................................54
Opening the vSphere Client .......................................................................................................................55
Deploying the OVF Template .............................................................................................................55
Logging In to Core-v ...................................................................................................................................56
Purchasing the Token and Receiving the Licenses .................................................................................57
Appendix A - SteelFusion Core Status Lights, Ports, and Technical Specifications .........................59
SteelFusion Core 3500 Specifications ........................................................................................................59
Status Lights and Ports ........................................................................................................................60
Technical Specifications .......................................................................................................................62
Power Requirements and Consumption...........................................................................................62
Environmental Specifications .............................................................................................................63
RAM Sizing............................................................................................................................................63
4
SteelFusion Core Installation and Configuration Guide
Contents
SteelFusion Core 3000 Specifications ........................................................................................................63
Status Lights and Ports ........................................................................................................................64
Technical Specifications .......................................................................................................................65
Power Requirements and Consumption...........................................................................................65
Environmental Specifications .............................................................................................................66
RAM Sizing............................................................................................................................................66
SteelFusion Core 2000 Specifications ........................................................................................................67
Status Lights and Ports ........................................................................................................................67
Technical Specifications .......................................................................................................................68
Power Requirements and Consumption...........................................................................................68
Environmental Specifications .............................................................................................................69
RAM Sizing............................................................................................................................................69
SteelFusion Core Installation and Configuration Guide
5
Contents
6
SteelFusion Core Installation and Configuration Guide
Preface
Welcome to the SteelFusion Core Installation and Configuration Guide. Read this preface for an overview of the
information provided in this guide and the documentation conventions used throughout, hardware and
software dependencies, additional reading, and contact information.

“About This Guide” on page 7

“Documentation and Release Notes” on page 8

“Safety Guidelines” on page 8

“Contacting Riverbed” on page 9
About This Guide
The SteelFusion Core Installation and Configuration Guide provides an overview of the SteelFusion block
storage optimization and consolidation system, and it shows you how to install and configure SteelFusion
Core. It also describes how to install SteelFusion Core Virtual Edition on the VMware ESX platform.
This guide includes information relevant to the following products:

Riverbed SteelFusion Core (Core)

Riverbed SteelFusion Core Virtual Edition (Core-v)

Riverbed SteelFusion Edge (Edge)

Riverbed Optimization System (RiOS)

Riverbed SteelHead (SteelHead)

Riverbed SteelCentral Controller for SteelHead Mobile (SteelCentral Controller for SteelHead Mobile)
This guide is intended to be used together with the following documentation:

SteelFusion Core Management Console User’s Guide

SteelFusion Design Guide

Network and Storage Card Installation Guide
SteelFusion Core Installation and Configuration Guide
7
Preface
Safety Guidelines
Audience
This guide is written for storage, virtualization, and network administrators familiar with administering
and managing storage arrays, snapshots, backups, virtual machines (VMs), Fibre Channel, and iSCSI.
Document Conventions
This manual uses the following standard set of typographical conventions.
Convention
Meaning
italics
Within text, new terms and emphasized words appear in italic typeface.
boldface
Within text, CLI commands, CLI parameters, and REST API properties appear in bold typeface.
Courier
Code examples appear in Courier font:
amnesiac > enable
amnesiac # configure terminal
<>
Values that you specify appear in angle brackets: interface <ip-address>
[]
Optional keywords or variables appear in brackets: ntp peer <ip-address> [version <number>]
{}
Elements that are part of a required choice appear in braces: {<interface-name> | ascii <string> |
hex <string>}
|
The pipe symbol separates alternative, mutually exclusive elements of a choice. The pipe symbol
is used in conjunction with braces or brackets; the braces or brackets group the choices and
identify them as required or optional: {delete <filename> | upload <filename>}
Documentation and Release Notes
To obtain the most current version of all Riverbed documentation, go to the Riverbed Support site at https:/
/support.riverbed.com.
If you need more information, see the Riverbed Knowledge Base for any known issues, how-to documents,
system requirements, and common error messages. You can browse titles or search for keywords and
strings. To access the Riverbed Knowledge Base, log in to the Riverbed Support site at https://
support.riverbed.com.
Each software release includes release notes. The release notes identify new features in the software as well
as known and fixed problems. To obtain the most current version of the release notes, go to the Software
and Documentation section of the Riverbed Support site at https://support.riverbed.com.
Examine the release notes before you begin the installation and configuration process.
Safety Guidelines
Follow the safety precautions outlined in the Safety and Compliance Guide when installing and setting up
your equipment.
Important: Failure to follow these safety guidelines can result in injury or damage to the equipment. Mishandling of
the equipment voids all warranties. Read and follow safety guidelines and installation instructions carefully.
8
SteelFusion Core Installation and Configuration Guide
Contacting Riverbed
Preface
Many countries require the safety information to be presented in their national languages. If this
requirement applies to your country, consult the Safety and Compliance Guide. Before you install, operate, or
service the Riverbed products, you must be familiar with the safety information. Refer to the Safety and
Compliance Guide if you do not clearly understand the safety information provided in the product
documentation.
Contacting Riverbed
This section describes how to contact departments within Riverbed.

Technical support - If you have problems installing, using, or replacing Riverbed products, contact
Riverbed Support or your channel partner who provides support. To contact Riverbed Support, open a
trouble ticket by calling 1-888-RVBD-TAC (1-888-782-3822) in the United States and Canada or
+1 415-247-7381 outside the United States. You can also go to https://support.riverbed.com.

Professional services - Riverbed has a staff of professionals who can help you with installation,
provisioning, network redesign, project management, custom designs, consolidation project design,
and custom coded solutions. To contact Riverbed Professional Services, email proserve@riverbed.com
or go to http://www.riverbed.com/services-training/Services-Training.html.

Documentation - The Riverbed Technical Publications team continually strives to improve the quality
and usability of Riverbed documentation. Riverbed appreciates any suggestions you might have about
its online documentation or printed materials. Send documentation comments to
techpubs@riverbed.com.
SteelFusion Core Installation and Configuration Guide
9
Preface
10
Contacting Riverbed
SteelFusion Core Installation and Configuration Guide
CHAPTER 1
Overview of SteelFusion Core
This chapter provides an overview of SteelFusion Core. It includes the following sections:

“Introducing SteelFusion” on page 11

“How SteelFusion Works” on page 12

“New Features in Core 4.3” on page 14

“Product Dependencies and Compatibility” on page 14

“Upgrading the Core Software” on page 17

“Replacing a Core Appliance” on page 20
Introducing SteelFusion
SteelFusion is a converged infrastructure solution, encompassing all branch services such as server, storage,
networking, and WAN optimization. It is a dual-ended system that comprises two logical components:
SteelFusion Edge and SteelFusion Core.
SteelFusion Core is a physical or virtual appliance in the data center that mounts all LUNs that need to be
made available to applications and servers at a remote location from the back-end storage array. SteelFusion
Edge provides a virtualized environment that hosts the branch application servers. Core appliances
communicate across the WAN with the Edge appliances at the branch.
SteelFusion delivers local user performance while enabling data centralization, instant recovery, and lower
total operating costs. Unlike traditional converged infrastructures, SteelFusion enables stateless branch
services. You can access applications that run locally in your branch while the primary data is centralized
in your data center. Decoupling computation from its underlying storage allows your applications to run in
a stateless mode, which reduces your branch footprint and centralizes management of your branch services.
With SteelFusion, you can extend a data center storage array to a remote location, even over a lowbandwidth link. This capability enables you to effectively deliver global storage infrastructure anywhere
you need it.
SteelFusion provides the following functionality:

Innovative block storage optimization ensures that you can centrally manage data storage while
keeping that data available to business operations in the branch, even in the event of a WAN outage.

A local authoritative cache ensures LAN-speed reads and fast cold writes at the branch.
SteelFusion Core Installation and Configuration Guide
11
Overview of SteelFusion Core
How SteelFusion Works

Integration with Microsoft Volume Shadow Copy Service enables consistent point-in-time data
snapshots and seamless integration with backup applications.

Integration with the snapshot capabilities of the storage array enables you to configure applicationconsistent snapshots through the SteelFusion Core Management Console.

Integration with industry-standard Challenge-Handshake Authentication Protocol (CHAP)
authenticates users and hosts.

A secure vault protects sensitive information using AES 256-bit encryption.

Solid-state disks (SSDs) that guarantee data durability and performance.

An active-active high-availability (HA) deployment option for Core ensures the availability of storage
array logical unit numbers (LUNs) for remote sites.

Customizable reports provide visibility to key utilization, performance, and diagnostic information.
How SteelFusion Works
SteelFusion enables branch office server systems to efficiently access storage arrays over the WAN. It is
typically deployed in conjunction with SteelHeads and is composed of the following components:

SteelFusion Core - A physical or virtual Core is deployed in the data center alongside SteelHeads and
a storage array. The Core mounts logical unit numbers (LUNs) provisioned for the branch offices from
a storage array, and manages block transfers between these LUNs and Edges. Additionally, SteelFusion
Core-v can mount LUNs via Fibre Channel. At the data center, the Core integrates with existing storage
systems and SteelHead implementations and connects dedicated LUNs with each Edge at the branch
office.

SteelFusion Edge - A standalone or high-availability Edge is deployed in the branch and presents the
LUNs mounted on the Core at the branch through iSCSI targets. The Edge can also host local LUNs
without a Core connection.

LUN - A unique identifier associated with individual storage devices or collections of storage devices
used with SCSI, iSCSI, or Fibre Channel interfaces.

Branch server - The branch-side servers access data from the SteelFusion system instead of a local
storage device. This server can also run as a Virtual Services Platform (VSP) VM on the local Edge.

Blockstore - A persistent and authoritative local cache of storage blocks on the Edge that caches the
writes on LUNs presented by the Edge. Blockstore also stores cached portions of the LUNs to quickly
serve read requests.

Data Center SteelHead - The data center-side SteelHead peer for WAN optimization.
12
SteelFusion Core Installation and Configuration Guide
How SteelFusion Works
Overview of SteelFusion Core
The following diagram shows a typical SteelFusion deployment.
Figure 1-1. Typical SteelFusion Deployment
SteelFusion initially populates the blockstore using the following methods:

First request - Blocks are added to the blockstore when first requested. The first request is subject to
standard WAN latency because it is the first time the blocks are being served. Subsequent traffic is
optimized. Reactive prefetch and policy-based prefetch minimizes these first requests.

On-demand prefetch - The Core observes block requests, intelligently predicts the blocks most likely
to be requested in the near future, and then requests those blocks from the data center LUN in advance.

Policy-based prefetch - Configured policies identify the blocks that are likely to be requested at a
given branch office site in advance. The Edge then requests those blocks from the data center LUN in
advance.
Blocks are transferred between Edges and Cores through an internal protocol. The Core then writes the
updates to the data center LUNs through the iSCSI or Fibre Channel protocol. Optionally, you can further
optimize traffic between the branch offices and the data center by implementing SteelHeads.
When the branch office server requests blocks, those blocks are served locally from the blockstore (unless
they are not present, in which case the Edge retrieves them from the data center LUN via the Core).
Similarly, newly written blocks are spooled to the local cache, acknowledged by the Edge to the branch
office server, and then asynchronously propagated to the data center. Because each Edge implementation is
linked to one or more dedicated LUNs at the data center, the blockstore is authoritative for both reads and
writes and can tolerate WAN outages without affecting cache coherency.
Riverbed strongly recommends that you read the SteelFusion Interoperability Matrix at https://
splash.riverbed.com/docs/DOC-4204.
For information on compatibility between RiOS, Edge, Core, and vSphere releases, see the Knowledge Base
article RiOS, SteelFusion Edge, SteelFusion Core and vSphere Release Matrix at https://
supportkb.riverbed.com/support/index?page=content&id=S:S27472.
SteelFusion Core Installation and Configuration Guide
13
Overview of SteelFusion Core
New Features in Core 4.3
New Features in Core 4.3
This section provides an overview of the new features available in Core 4.3.

Dashboard - The new Core dashboard gives you an instant and dynamic view into key statistics for
your enterprise, such as alarms, cache efficiency, and LUN and Edge performance. For details, see the
SteelFusion Core Management Console User’s Guide.

Cloud Gateway Support - Consolidate your branch data to the cloud using Amazon Storage Gateway
(AWS S3 backend) or Microsoft StorSimple (Azure backend) as virtual appliances in the data center.
This consolidation will extend the benefits of the hybrid cloud to your branch infrastructure, giving
you the flexibility of augmenting your data center storage with cloud storage. For details, see the
SteelFusion with StorSimple Hybrid Cloud Storage Solution Guide and SteelFusion with Amazon Web Services
Storage Gateway Solution Guide.
Product Dependencies and Compatibility
This section provides information about product dependencies and compatibility. It includes the following
information:

“Hardware and Software Dependencies” on page 14

“Core-v RAM and CPU Requirements” on page 15

“Firewall Requirements” on page 15

“SNMP-Based Management Compatibility” on page 15

“Ethernet Network Compatibility” on page 15

“iSCSI-Compliant Storage Array Interoperability” on page 16
Hardware and Software Dependencies
The following table summarizes the hardware and software requirements for the Core.
Riverbed Component
Hardware and Software Requirements
Core appliance
19-inch (483-mm) two-post or four-post rack.
SteelFusion Core Management Console
Any computer that supports a web browser with a color image
display.
The SteelFusion Core Management Console has been tested with
Mozilla Firefox Extended Support Release version 31.0, Google
Chrome, and Microsoft Internet Explorer 9.0.
JavaScript and cookies must be enabled in your web browser.
SteelFusion Edge Management Console
Any computer that supports a web browser with a color image
display.
The SteelFusion Edge Management Console has been tested with
Mozilla Firefox Extended Support Release version 31.0, Google
Chrome, and Microsoft Internet Explorer 9.0.
JavaScript and cookies must be enabled in your web browser.
14
SteelFusion Core Installation and Configuration Guide
Product Dependencies and Compatibility
Overview of SteelFusion Core
Core-v RAM and CPU Requirements
For details about Core-v, including all hardware and software requirements, see Chapter 4, “Installing
Core-v.” .
Firewall Requirements
Riverbed recommends that you deploy the Core behind your firewall. Ports 22, 25, 443, 7950, 7951, 7952,
7953 and 7954, and 7970 must be open.
Virus scanning, deep packet inspection (DPI) and other features that scan the traffic should be disabled.
When specifying IP addresses for firewall rules, Riverbed recommends that you add all the interface IP
addresses of all Edge devices including in-path IPs. If the Edges are set up for high availability, ensure that
you also add the standby Edge IP address.
SNMP-Based Management Compatibility
The Core supports a proprietary Riverbed MIB accessible through SNMP. SNMPv1 (RFCs 1155, 1157, 1212,
and 1215), SNMPv2c (RFCs 1901, 2578, 2579, 2580, 3416, 3417, and 3418), and SNMPv3 are supported,
although some MIB items might be accessible only through SNMPv3 and SNMPv2.
SNMP support allows the Core to be integrated into network management systems such as HewlettPackard OpenView Network Node Manager, BMC Patrol, and other SNMP-based network management
tools.
Ethernet Network Compatibility
The Core appliance supports the following Ethernet networking standards:

Ethernet Logical Link Control (LLC) (IEEE 802.2 - 1998)

Fast Ethernet 10BASE-TX (IEEE 802.3 - 2008)

Gigabit Ethernet over Copper 1000BASE-T and Fiber 1000BASE-SX (LC connector) and Fiber
1000BASE-LX (IEEE 802.3 - 2008)

10-Gigabit Ethernet over Fiber 10GBASE-LR Single Mode and 10GBASE-SR Multimode (IEEE 802.3 2008)
The Core appliance ports support the following connection types and speeds:

Primary - 10BASE-T, 100BASE-T, and 1000BASE-T, autonegotiating

Auxiliary - 10BASE-T, 100BASE-T, and 1000BASE-T, autonegotiating

ETHx_x - 10/100/1000BASE-T or 1000BASE-SX or 1000BASE-LX, depending on configuration.
The Core appliance supports VLAN tagging (IEEE 802.1Q - 2005). It does not support the Cisco Inter-Switch
Link (ISL) protocol.
All copper interfaces are autosensing for speed and duplex (IEEE 802.3 - 2005).
The Core appliance automatically negotiates speed and duplex mode for all data rates and supports full
duplex mode and flow control (IEEE 802.3 - 2005).
The Core appliance with a Gigabit or 10-Gigabit Ethernet card supports jumbo frames on in-path and
primary ports.
SteelFusion Core Installation and Configuration Guide
15
Overview of SteelFusion Core
Product Dependencies and Compatibility
iSCSI-Compliant Storage Array Interoperability
The Core appliance can interoperate with any iSCSI-compliant storage array. However, support for
snapshots and other features can be limited. Fibre Channel connectivity is available for SteelFusion Core-v
deployments.
Riverbed strongly recommends that you read the SteelFusion Interoperability Matrix at https://
splash.riverbed.com/docs/DOC-4204, where you will find a list of storage systems qualified by the
original storage vendor and Riverbed internal engineers and field-tested by Riverbed customers and
partners.
16
SteelFusion Core Installation and Configuration Guide
Upgrading the Core Software
Overview of SteelFusion Core
Upgrading the Core Software
This section provides information about upgrading your Core software and using the Riverbed Host Tools
installer. It includes the following information:

“Upgrading the Core Software Version” on page 17

“Downgrading the Core Software Version” on page 19

“Using the Riverbed Host Tools Installer” on page 19
Core 4.3 is backward compatible with previous Core versions. However, if you are running different
versions of Core software in your network, the releases may support different features and you will not be
able to take full advantage of the latest enhancements. To obtain the full benefits of the new features in Core
4.3, Riverbed recommends that you upgrade both Core and Edge software.
Upgrading the Core Software Version
Follow these steps to upgrade your Core software. These instructions assume you are familiar with the
Core, the CLI, and the SteelFusion Core Management Console.
Before upgrading, Riverbed recommends exporting your configuration as a precautionary measure and to
ensure that the most current configuration is saved and easily accessible.
Note: When upgrading the Core software version, the upgrade path must follow all major releases. For example, if you
are upgrading the software from version 3.5 to 4.0, you must upgrade from 3.5 to 3.6 to 4.0.
SteelFusion Core Installation and Configuration Guide
17
Overview of SteelFusion Core
Upgrading the Core Software
To export the current configuration
1. Choose Configure > Wizards: Export to start the Export Configuration wizard.
Figure 1-2. Export Configuration Wizard
2. Click Export Configuration.
3. Click Exit.
To upgrade the Core software
1. Download the software image from the Riverbed Support site to a location such as your desktop.
2. Log in to the SteelFusion Core Management Console using the Administrator account (admin).
3. Choose Settings > Maintenance: Software Upgrade to display the Software Upgrade page.
4. Select one of the following options under Install Upgrade:
–
From URL - Type the URL that points to the software image in the text box. You can use HTTP,
HTTPS, FTP, or SCP formats for the URL.
–
From Local File - Browse your file system and select the software image.
–
Schedule Upgrade for Later - Schedules the upgrade process. Specify the date and time to run the
upgrade using the following format: yyyy/mm/dd hh:mm:ss.
5. Click Install.
The system installs the image in the backup partition and sets the option to load the backup partition
version on reboot.
6. Choose Settings > Maintenance: Reboot/Shutdown and click Reboot.
18
SteelFusion Core Installation and Configuration Guide
Upgrading the Core Software
Overview of SteelFusion Core
The device can take a few minutes to reboot because the software is configuring the recovery flash
device. Do not press Ctrl+C, unplug, or otherwise shut down the system during this first boot. There is
no indication displayed during the system boot that the recovery flash device is being configured.
After the reboot, the Home page, Software Upgrade, and Support pages of the Management Console
display the Core version upgrade.
Note: If you are upgrading to version 4.3, the new Dashboard will appear after you clear your browser cache.
Downgrading the Core Software Version
If you are downgrading to a previous version of the Core software, you must downgrade to a version of the
software that has previously run on your system.
Note: If the previous version of the Core software does not support any currently configured features, the downgrade
will not be successful until you remove or disable these features. After a failed downgrade attempt, the Core will
display the unsupported features in the system logs, which you can access by choosing Reports > Logs: System Logs.
Using the Riverbed Host Tools Installer
As of version 4.3, the Riverbed Host Tools installer is available on the Riverbed Support site at https://
support.riverbed.com. This installer provides one central location for SteelFusion’s Windows plug-ins
(Riverbed Turbo boot plug-in, Riverbed Hardware Snapshot Provider, and Riverbed Branch Recovery
Agent).
Note: The installer is supported on Windows 2008 Release 2, Windows 2012, and Windows 2012 Release 2.
To install Riverbed host tools
1. Download the Riverbed Host Tools installer from the Riverbed Support site at https://
support.riverbed.com.
2. Run the installer.
3. Specify one or more of the three components to install and follow the prompts.
You can choose from Turbo Boot plug-in, Riverbed Hardware Snapshot Provider, and Branch Recovery
Agent.
Note: The turbo boot installer is supported on Windows 2012 Release 2 as of Core version 4.3.
4. Once you have installed the plugins, reboot the VM.
SteelFusion Core Installation and Configuration Guide
19
Overview of SteelFusion Core
Replacing a Core Appliance
Replacing a Core Appliance
This section describes how to replace a Core appliance in the event of failure so you can seamlessly continue
operations. To minimize downtime and data loss when recovering from a failure, Riverbed strongly
recommends that you deploy two Core appliances as a high availability pair.
For more detailed information about high availability and Core and Edge appliance replacement scenarios,
see the SteelFusion Design Guide.
Basic Steps
This table describes the basic steps needed to replace a Core appliance, followed by detailed procedures.
Task
Reference
1. Stop the SteelFusion Core service on the failed Core appliance
and the replacement Core.
“To stop the SteelFusion Core service” on page 20
2. Export the current configuration from the failed Core
appliance.
“To export the current configuration” on page 21
3. Back up the system configuration settings on the replacement
Core appliance.
“To back up the system configuration settings on
the replacement Core appliance” on page 22
4. Import the saved configuration into the replacement Core
appliance.
“To import the configuration into the
replacement Core” on page 23
5. If you are replacing a high availability Core appliance, restart
service on the replacement Core.
“To restart the SteelFusion Core service” on
page 24
6. If you are replacing a standalone Core appliance, reboot the
Core.
“To reboot the Core after saving the
configuration”
To stop the SteelFusion Core service
1. On the failed Core appliance, choose Settings > Maintenance: Service to display the Service page.
Figure 1-3. Service Page
2. Click Stop to stop the SteelFusion Core service.
3. Repeat Steps 1 and 2 on the replacement Core appliance.
20
SteelFusion Core Installation and Configuration Guide
Replacing a Core Appliance
Overview of SteelFusion Core
To export the current configuration
1. Choose Configure > Wizards: Export to start the Export Configuration wizard.
Figure 1-4. Export Configuration Wizard
2. Click Export Configuration.
3. Click Exit.
SteelFusion Core Installation and Configuration Guide
21
Overview of SteelFusion Core
Replacing a Core Appliance
To back up the system configuration settings on the replacement Core appliance
1. On the replacement Core, choose Settings > System Settings: Configurations to display the
Configurations page.
Figure 1-5. Configurations Page
2. Select the working configuration to display it in a pop-up window.
3. Press Ctrl+S to save the configuration file.
You can also copy, paste, and save the configuration file into a text editor.
If you are not able to export the configuration, please contact Riverbed Support at
support@riverbed.com.
22
SteelFusion Core Installation and Configuration Guide
Replacing a Core Appliance
Overview of SteelFusion Core
To import the configuration into the replacement Core
1. On the replacement Core, choose Configure > Wizards: Import to display the Import Configuration
Wizard.
Figure 1-6. Import Configuration Wizard
2. Select the Local File option and click Browse to navigate to the saved configuration file.
3. Clear the Import Shared Data Only check box.
4. Click Import Configuration.
Note: If importing the configuration leads to lost SSH or web access, obtain console access to the new Core and reset
the management IP address and default gateway of the new Core. You can find this information in the exported
configuration file.
5. Click Exit.
SteelFusion Core Installation and Configuration Guide
23
Overview of SteelFusion Core
Replacing a Core Appliance
To restart the SteelFusion Core service
1. On the replacement Core appliance, choose Settings > Maintenance: Service to display the Service page.
Figure 1-7. Service Page
2. Click Start to restart the service using the imported configuration.
3. From a console, try connecting to the replacement Core appliance.
To reboot the Core after saving the configuration
1. Choose Settings > Maintenance: Reboot/Shutdown.
Figure 1-8. Reboot / Shutdown Page
2. Click Reboot.
24
SteelFusion Core Installation and Configuration Guide
CHAPTER 2
Managing Riverbed Licenses
This chapter describes the Riverbed licensing methods and how to manage Riverbed licenses. It includes
the following sections:

“Riverbed Licensing Methods” on page 25

“Automatic Licensing” on page 26

“Manual and Token Licensing” on page 27
Riverbed Licensing Methods
A license is a string issued by Riverbed that embeds information that ties the license to data to prevent
tampering. After you install the license, the system saves it in the configuration database and enables the
functionality associated with the license. Riverbed employs the following licensing methods:

Automatic licensing - Once you connect your Core appliance to the network, it automatically contacts
the Riverbed Licensing Portal, which downloads and installs the licenses.

Manual licensing - You can manually fetch and activate licenses for Riverbed products using the
Riverbed Licensing Portal. Go to https://licensing.riverbed.com and follow the instructions to retrieve
license keys. After you manually retrieve your license keys, you need to install them on the appropriate
appliance.

Token method - You use tokens to activate Riverbed software, such as the Virtual SteelCentral
Controller for SteelHead Mobile, SteelHead (virtual edition), and Core-v. For detailed information, see
the respective installation guides for these products.

Factory licensing - You can have all your Riverbed licenses installed at the factory for a small fee.
SteelFusion Core Installation and Configuration Guide
25
Managing Riverbed Licenses
Automatic Licensing
Automatic Licensing
Automatic licensing allows Core, once connected to the network, to automatically contact the Riverbed
Licensing Portal to retrieve and install license keys onto the appliance. Automatic licensing simplifies
inventory management and provides an automated mechanism of fetching licenses for Riverbed products
without having to manually activate individual appliances and licenses.
If you are behind a firewall, you can retrieve licenses at the Riverbed Licensing Portal using the email option
or by downloading an XML file to the SteelCentral Controller for SteelHead. For detailed information, see
“Retrieving Licenses Using the Riverbed Licensing Portal” on page 27.
Automatic licensing also works over a web proxy. For details about setting up a web proxy, see the
SteelFusion Core Management Console User’s Guide.
Note: If automatic licensing fails, an error message appears in the SteelFusion Core Management Console. Go to the
Riverbed Licensing Portal and follow the instructions for retrieving your licenses.
To view licenses on a new Core appliance

Connect the new Core appliance to the network.
Core automatically connects to the Riverbed Licensing Portal and downloads and installs the licenses.
The Management Console Licensing page displays a success message, or the Alarm Status page
reports an actionable error message.
To replace expired licenses

Purchase new downloadable licenses to replace the expired license.
At the time of the next scheduled automatic license fetch, the Core automatically contacts the Riverbed
License Portal and downloads the new licenses. The Management Console Licensing page displays a
success message or the Alarm Status page reports an actionable error message. You do not need to
delete the expired license. The system uses the license with the latest expiration date.
To fetch a license on demand
1. In the Management Console, choose Settings > Maintenance: Licenses to display the Licenses page.
2. Click Fetch Updates Now.
The Management Console Licensing page displays a success message, or the Alarm Status page
reports an actionable error message.
Note: Only users with administrative privileges can fetch and install licenses. For detailed information about
administrator and monitor users, see the SteelFusion Core Management Console User’s Guide.
26
SteelFusion Core Installation and Configuration Guide
Manual and Token Licensing
Managing Riverbed Licenses
Manual and Token Licensing
You can retrieve and manage Riverbed licenses using the Riverbed Licensing Portal. After you retrieve the
licenses, you need to install them.
Retrieving Licenses Using the Riverbed Licensing Portal
The licensing portal requires a unique product identifier to retrieve a license. Depending on the product,
the identifier can be a serial number, license request key (activation code), or a token. The steps to retrieve
a license vary based on the product identifier. Online instructions guide you through the process.
To retrieve your licenses for an appliance using a serial number
1. Go to the Riverbed Licensing Portal at https://licensing.riverbed.com.
2. Enter your appliance serial number as your unique product identifier.
The serial number is on a label located on your device, and it also appears in the Support tab of the
Management Console.
3. Click Next.
4. Provide the contact information for the license, including your name and email.
5. Click Submit.
The Licensing Portal displays license information for all the products purchased with the serial
number you specified.
6. Click a serial number to see license details.
7. Optionally, if you are behind a firewall, type the email address in the Email address text box and click
Email Keys to have the license keys emailed to you.
8. Optionally, if you are behind a firewall, click Download XML to download an XML file. You can import
the XML file using the SteelCentral Controller for SteelHead.
Note: Click New Search to look for additional license records.
SteelFusion Core Installation and Configuration Guide
27
Managing Riverbed Licenses
Manual and Token Licensing
To retrieve your licenses for a virtual appliance using a token
1. Go to the Riverbed Licensing Portal at https://licensing.riverbed.com.
2. Enter your token as the unique product identifier.
3. To submit more than one product identifier, click Add.
4. Click Next.
5. Verify the token and enter your license key request (activation code).
You need a license request key (activation code) to generate a license key. You can generate a license
request key from the Management Console or command line using an available token.
6. Click Next.
Licenses appear on the screen and are emailed to the customer address linked to the token.
Installing Your License Keys
If you manually retrieve your license keys, you need to install them on the appropriate appliance.
To install a license using the CLI
1. Connect to the CLI of the appliance and enter configuration mode.
For details, see the Riverbed Command-Line Interface Reference Manual.
2. At the system prompt, enter the following commands:
license install <license-key>
write memory
To install a license using the Management Console
1. Connect to the SteelFusion Core Management Console.
For details, see the SteelFusion Core Management Console User’s Guide.
2. Choose Settings > Maintenance: Licenses to display the Licenses Page.
3. In the Licenses Text Box, copy and paste the license key provided by the Riverbed Licensing Portal into
the text box.
Separate multiple license keys with a space, Tab, or Enter.
28
SteelFusion Core Installation and Configuration Guide
CHAPTER 3
Configuring SteelFusion Core
This chapter describes how to install and configure Core. It includes the following sections:

“Choosing a Network Deployment” on page 30

“Checking Your Inventory” on page 30

“Preparing Your Site for Installation” on page 31

“Powering On the Core” on page 33

“Configuring the Core” on page 34

“Viewing Version Information” on page 38

“Configuring the Core with Edges” on page 38
For details about installing Core-v, see Chapter 4, “Installing Core-v.”
Important: Read and follow the safety guidelines described in the Safety and Compliance Guide. Failure to follow these
safety guidelines can result in damage to the equipment.
SteelFusion Core Installation and Configuration Guide
29
Configuring SteelFusion Core
Choosing a Network Deployment
Choosing a Network Deployment
The Core is typically deployed on a LAN, with communication between appliances taking place over a
private WAN or VPN. Because communication between Edges and the Core typically takes place over a
secure WAN, it is not necessary to configure company firewalls to support Core-specific ports.
To configure your firewall to support Core-specific ports, see “Firewall Requirements” on page 15.
For detailed information about your deployment options and best practices for deploying SteelFusion Core,
see the SteelFusion Design Guide.
Before you begin the installation and configuration process, you must select a network deployment.
Figure 3-1. Typical SteelFusion Deployment
Checking Your Inventory
Your shipping carton contains the following items:

SteelFusion Core

One standard Ethernet straight-through cable

One serial null-modem cable

One or two power cables (depending on your order)
Aside from country-specific requirements, all systems ship with the same power cable. The power
cable has an IEC 60320 C13 plug on one end (to connect to the Core) and a country-specific plug that
fits the wall socket for that country. If a system has two power supplies, it ships with two suitable
cables.
You must always connect the Core using either the cable in the accessories box or another cable that is
approved for use by the IEC in the country in which the appliance is connected.
30
SteelFusion Core Installation and Configuration Guide
Preparing Your Site for Installation
Configuring SteelFusion Core
You cannot connect one Core directly to multiphase outlets. You must use a rack PDU or power strip
that provides the appropriate three-prong outlet (hot/neutral/ground). For details, see the Knowledge
Base solution number S13425 (https://supportkb.riverbed.com/support/
index?page=content&id=S13425&actp=search).

One Phillips-head screwdriver

One mounting kit

Documentation kit
If any items are damaged or missing, notify Riverbed Support at https://support.riverbed.com for
replacement or repair.
Preparing Your Site for Installation
The Core is shipped completely assembled with all the equipment parts in place and securely fastened.
Before you install the Core, make sure that your site meets the following requirements:

It is a standard electronic environment where the ambient temperature does not exceed 104º Fahrenheit
(40º Celsius) and the relative humidity does not exceed 80 percent (noncondensing). For detailed
information, see Appendix A, “SteelFusion Core Status Lights, Ports, and Technical Specifications”.

Ethernet connections are available within the standard Ethernet limit.

There is available space on a four-post 19-inch rack. For details about installing the Core to a rack, see
the Rack Installation Guide or the printed instructions that were shipped with the system.

A clean power source is available, dedicated to computer devices and other electronic equipment.

The rack is a standard 19-inch Telco-type mounting rack.
Note: Riverbed recommends that you use a four-post mounting rack for 2U systems.
Note: If your rack requires special mounting screws, contact your rack manufacturer.
Core Ports
The following table summarizes the ports used to connect the Core to your network.
Port
Description
Console
Connects the serial cable to a terminal device. You establish a serial connection to a
terminal emulation program for console access to the configuration wizard and the Core
CLI.
Primary (PRI)
The PRI connects the Core to a VLAN switch through which users connect to the
Management Console and the Core CLI. This port is also typically used for
communication with Edges.
Note: The primary and auxiliary ports cannot share the same network subnet.
SteelFusion Core Installation and Configuration Guide
31
Configuring SteelFusion Core
Port
Auxiliary (AUX)
Preparing Your Site for Installation
Description
The AUX port connects the Core to the management VLAN.
Note: The primary and auxiliary ports cannot share the same network subnet.
ETH0_1 through
ETH0_3
Connects the ETH0_1, ETH0_2, ETH0_3 ports of the Core and the LAN switch using a
straight-through cable.
Note: If Core is deployed between two switches, all ports must be connected with
straight-through cables.
Figure 3-2. Core Ports
NIC Interface Naming Conventions
The interface names for the network interface cards are a combination of the slot number and the port pairs
(<slot>_<pair>, <slot>_<pair>). For example, if a four-port network interface card is located in slot 1 of your
appliance, the interface names are ETH1_0, ETH1_1, ETH1_2, and ETH1_3, respectively. Alternatively, if the
network interface card is located in slot 2 of your appliance, the interface names are ETH2_0, ETH2_1,
ETH2_2, and ETH2_3, respectively.
For detailed information about installing additional NICs, see the Network and Storage Card Installation
Guide.
32
SteelFusion Core Installation and Configuration Guide
Powering On the Core
Configuring SteelFusion Core
Powering On the Core
The following section describes how to connect the AC power and how to power on the system.
Caution: In European electrical environments you must ground (earth) the green/yellow tab on the power cord to
avoid the risk of electrical shock.
To power on the system
1. Ensure that the system and master power switch is in the off position on the rear of the Core.
2. Plug the AC power cords into the Core.
Figure 3-3. Connecting the AC Power
3. Plug the AC power cord into an uninterrupted AC power source.
4. Press the master power switch on the Core for 4 to 6 seconds.
If Core does not immediately power on, press the system power switch again.
5. Check the status lights on the Core.
For detailed information about the status lights, see Appendix A, “SteelFusion Core Status Lights,
Ports, and Technical Specifications”.
Note: The system takes about 2 to 5 minutes to boot.
SteelFusion Core Installation and Configuration Guide
33
Configuring SteelFusion Core
Configuring the Core
Configuring the Core
In a physical out-of-path deployment, the Core is not in the direct path between the client and the server.
Configuration Wizard
The configuration wizard automatically starts when you log in to the CLI for the first time.
The following rules apply to the configuration wizard:

Click Enter to enter the default value.

Click the ? icon for help.

Press Ctrl+B to go back to the previous step.
If you quit the configuration wizard, you can restart it from the Core CLI. You must be in configuration
mode to restart the configuration wizard.
To run the configuration wizard
1. Plug the serial cable into the Serial/Console port and a terminal.
2. Start your terminal emulation program, such as Tera Term Pro.
The terminal device must have the following settings:

Baud rate: 9600 bps

Data bits: 8

Parity: none

Stop bits: 1

VT100 emulation

No flow control
Riverbed recommends that you connect the console port to a device that logs output. Even though this
connection is not a requirement, it can help you to identify problems with the system.
34
SteelFusion Core Installation and Configuration Guide
Configuring the Core
Configuring SteelFusion Core
3. Log in as administrator user (admin) and enter the default password (password). For example:
login as: admin
Sent username "admin"
password: password
The configuration wizard automatically starts after you have entered the login and default password.
After you have established a connection, you configure the Core using the configuration wizard.
4. To start the configuration wizard, enter yes at the system prompt.
Do you want to use the configuration wizard for initial configuration? yes
5. Complete the configuration wizard steps as described in the following table.
Wizard Prompt
Description
Example
Step 1: Host name?
Enter the hostname for the Core.
hostname? amnesiac
Step 2: Use DHCP on the
primary interface?
You are given the option to enable the
DHCP to automatically assign an IP
address to the primary interface for
the Core.
Use DHCP? no
Riverbed recommends that you do not
set DHCP.
The default value is no.
Step 3: Primary IP address?
Enter the IP address for the Core.
Primary IP address? 10.64.8.42
Step 4: Netmask?
Enter the netmask address.
Netmask? 255.255.x.x
Step 5: Default gateway?
Enter the default gateway for the
Core.
Default gateway? 10.x.8.x
Step 6: Primary DNS server?
Enter the primary DNS server IP
address.
Primary DNS server? 10.64.x.x
Step 7: Domain name?
Enter the domain name for the
network where the Core is to reside.
Domain name? zuk.lab.nbttech.com
If you set a domain name, you can
enter hostnames in the system
without the domain name.
Step 8: Admin password?
Riverbed strongly recommends that
you change the default administrator
password at this time. The password
must be a minimum of six characters.
Admin password? xxxyyy
The default administrator password is
password.
SteelFusion Core Installation and Configuration Guide
35
Configuring SteelFusion Core
Configuring the Core
6. The system confirms your settings.
You have entered the following information:
1. Hostname: amnesiac
2. Use DHCP on primary interface: no
3. Primary IP address: 10.64.8.42
4. Netmask: 255.255.x.x
5. Default gateway: 10.x.8.x
6. Primary DNS server: 10.64.x.x
7. Domain name: zuk.lab.nbttech.com
8. Admin password: xxxyyy
To change an answer, enter the step number to return to.
Otherwise hit <enter> to save changes and exit.
Choice:
The Core configuration wizard automatically saves your configuration settings.
7. To log out of the system, enter the following command at the system prompt:
amnesiac > exit
To restart the configuration wizard

Enter the following set of commands at the system prompt:
amnesiac > enable
amnesiac > # configure terminal
amnesiac > (config) # configuration jump-start
For detailed information about the CLI, see the Riverbed Command-Line Interface Reference Manual.
Connecting Core to Your Network
You use standard Ethernet straight-through cables to connect to your network in an out-of-path
configuration. Make sure that you use the correct cable to establish your network connections:

Straight-through cable - Primary and Ethernet ports on the appliance to the LAN switch.
To connect to your network
1. Plug the straight-through cable into the primary port of the Core and the LAN switch.
This port can be any one on your LAN switch configured to connect to a host.
Figure 3-4. Connecting the Primary Port to the LAN Switch
36
SteelFusion Core Installation and Configuration Guide
Configuring the Core
Configuring SteelFusion Core
Connecting to the SteelFusion Core Management Console
After you configure the Core, you can check and modify your configuration settings and view performance
reports and system logs in the Management Console. You can connect to the Management Console through
any supported web browser.
To connect to the SteelFusion Core Management Console, you must know the host, domain, and
administrator password that you assigned in the configuration wizard.
Note: Cookies and JavaScript must be enabled in your web browser.
To connect to the SteelFusion Core Management Console
1. Specify the URL for the SteelFusion Core Management Console in the location box of your web browser:
<protocol>://<host>.<domain>
–
<protocol> is http or https. HTTPS uses the SSL protocol to ensure a secure environment. If you use
HTTPS to connect, you are prompted to inspect and verify the SSL key.
–
<host> is the hostname you assigned to the Core during initial configuration. If your DNS server
maps that IP address to a name, you can specify the DNS name.
–
<domain> is the full domain name for the Core.
Note: Alternatively, you can specify the IP address instead of the host and domain.
The SteelFusion Core Management Console appears, displaying the Login page.
Figure 3-5. Login Page
2. In the Username text box, type the user login.
The default login is admin. Users with administrative (admin) privileges can configure and administer
the Core. Users with monitor privileges can view the Core reports, user logs, and change their own
password. A monitor user cannot make configuration changes.
3. In the Password text box, type the password you assigned in the Core’s configuration wizard. (Core is
shipped with the default password: password.)
SteelFusion Core Installation and Configuration Guide
37
Configuring SteelFusion Core
Viewing Version Information
4. Click Sign In to display the Home page.
The Home page summarizes the current status of your system.
Viewing Version Information
You can view version information by logging in to the CLI and entering the show version all command.
For example:
amnesiac > show version all
Product name:
rbt_dva
Product release:
4.0.0
Build ID:
#40_2
Build date:
2015-02-16 17:30:28
Build arch:
x86_64
Built by:
root@basel
Uptime:
Product model:
System memory:
Number of CPUs:
CPU load averages:
14d 21h 0m 46s
3500
334 MB used / 3611 MB free / 3945 MB total
2
0.00 / 0.01 / 0.00
Configuring the Core with Edges
This section describes the procedures for configuring the connection between the Core and the iSCSI
targets, and the Core and the Edges. It includes the following sections:

“Prerequisites” on page 38

“Configuring the Edge” on page 39

“Configuring Storage” on page 40

“Configuring the Core” on page 40

“Performing Additional Configuration Settings” on page 49
Prerequisites
Before you can connect an Edge to the Core, ensure the following conditions and procedures have been
completed:

Assign an IP address or hostname to the Core.

Determine the iSCSI Qualified Name (IQN) to be used for the Core.
When you configure the Core, you will set this value in the initiator configuration.


38
Set up your storage array:
–
Register the Core IQN.
–
Configure the iSCSI portal, targets, and LUNs, with the LUNs assigned to the Core IQN.
Assign an IP address or hostname to the Edge.
SteelFusion Core Installation and Configuration Guide
Configuring the Core with Edges
Configuring SteelFusion Core
Configuring the Edge
Before you configure the Core, Riverbed recommends that you configure branch storage on the Edge. All
hypervisor storage is provided by RiOS through iSCSI using Riverbed BlockStream technology. A
hypervisor has no local disks for storage. When a Core is connected to the Edge, you can use it to manage
remote storage at your data center. This configuration allows future expandability.
This section shows you how to:

connect the Edge to the Core by assigning a self-identifier for the Edge functionality.

configure storage to allow space for the Edge blockstore.

configure the Core.
Connecting the Edge to the Core
You configure connectivity to the Core in the Edge’s Storage page. The Edge module virtually presents one
or more iSCSI targets in the branch that can be used by services and systems running both within the
hypervisor as well as externally to the Edge. Edge features the BlockStream, which is essentially an on-disk
local cache that mirrors the complete persistent storage on the Core-side LUN(s).
Note: The Core must be running version 3.6 or later.
To connect an Edge to a Core
1. On the Edge, choose Storage > Storage Edge Configuration to display the Storage page.
2. Use the controls to complete the configuration as described in the following table.
Control
Description
Hostname/IP
Specify the Core’s hostname or IP address.
SteelFusion Edge Identifier
Specify a value by which the current appliance can be recognized by the Core.
You may use any value: for example, the appliance’s hostname.
Important: The Edge identifier is case sensitive.
Important: If failover is configured, both appliances must use the same selfidentifier. In this case, you can use a value that represents the group of appliances.
Local Interface
A drop-down list of currently configured local interfaces for the current Edge to
use when connecting to the Core. Click Add Interface to add another interface.
Add Core
Click to add the Core configuration.
3. Proceed to “Configuring the Core” on page 40.
After performing initial configuration of the Core, you return to the Edge to confirm the connection.
For details, see “Confirming the Connection to an Edge” on page 47.
SteelFusion Core Installation and Configuration Guide
39
Configuring SteelFusion Core
Configuring the Core with Edges
Configuring Storage
You can configure the disk storage to allow space for the Edge blockstore using the hypervisor installer on
the Edge. Free disk space is divided between the hypervisor and the Edge blockstore. For details on the
hypervisor installer, see “Using the Hypervisor Installer” in the SteelFusion Edge Management Console User’s
Guide.
Configuring the Core
This section describes the procedures for configuring the Core using the SteelFusion Core Management
Console.
Note: After initial setup, you can further modify the Core configuration using the relevant pages in the SteelFusion Core
Management Console.
This section describes the following tasks:

“Performing Initial Configuration with the Settings Wizard” on page 40

“Configuring Network Settings” on page 40

“Mapping LUNs to Edges” on page 42

“Confirming the Connection to an Edge” on page 47
Performing Initial Configuration with the Settings Wizard
The SteelFusion Core Management Console provides a setup wizard that enables you to quickly configure
your network, time zone, and initiator settings, and to map LUNs to Edges.
Note: You can modify all the settings performed in the Settings Wizard elsewhere in the SteelFusion Core Management
Console, as indicated in each of the procedures.
The first time you log in to the Core appliance, the setup wizard displays automatically. You can also access
it manually.
Configuring Network Settings
The Settings Wizard enables you to quickly configure basic network and time zone settings.
40
SteelFusion Core Installation and Configuration Guide
Configuring the Core with Edges
Configuring SteelFusion Core
To set the initial network configuration
1. Choose Configure > Wizards: Initial Setup to display the Settings Wizard.
Figure 3-6. Settings Wizard - System Settings Page
2. Configure the System Settings using the controls described in the following table.
Control
Description
Hostname
Specify the IP address or hostname of the Core.
Note: After initial configuration, this setting can be modified in the Configure >
Networking: Host Settings page in the SteelFusion Core Management Console.
DNS Server IP Address
Specify the IP address for the primary name server.
Note: After initial configuration, this setting can be modified in the Configure >
Networking: Host Settings page in the SteelFusion Core Management Console.
Obtain IPv4 Address
Automatically
Specify this option to automatically obtain the IPv4 address from a DHCP server. A
DHCP server must be available so that the system can request the IP address from it.
Note: After initial configuration, this setting can be modified in the Configure >
Networking: Host Settings page in the SteelFusion Core Management Console.
Specify IPv4 Address
Manually
Specify this option if you do not use a DHCP server to set the IP address. Specify the
following settings:
• IPv4 Address - Specify an IPv4 address.
• IPv4 Subnet Mask - Specify a subnet mask.
• Default IPv4 Gateway - Specify the primary gateway IP address. The primary
gateway must be in the same network as the primary interface.
Note: After initial configuration, this setting can be modified in the Configure >
Networking: Management Interfaces page in the SteelFusion Core Management Console.
Time Zone
Select the time zone from the drop-down list.
Note: After initial configuration, this setting can be modified in the Configure >
Networking: Management Interfaces page in the SteelFusion Core Management Console.
3. Click Next to save the settings and display the Confirmation page.
SteelFusion Core Installation and Configuration Guide
41
Configuring SteelFusion Core
Configuring the Core with Edges
The Confirmation page summarizes the settings you configured in the preceding pages.
Figure 3-7. Settings Wizard - Confirmation Page
4. Click Back to go back and modify the settings or click Save and Apply to complete this set of
configuration settings.
The Finish page displays.
Mapping LUNs to Edges
The LUN mapping pages enable you to quickly add LUNs, Edges, and iSCSI portals and targets to the Core
configuration.
42
SteelFusion Core Installation and Configuration Guide
Configuring the Core with Edges
Configuring SteelFusion Core
To map LUNs to Edges
1. Choose Configure > Wizards: LUN Mapping to display the LUN Mapping Wizard.
Figure 3-8. LUN Mapping Wizard
2. In the iSCSI Initiator Name field, specify the iSCSI Qualified Name (IQN) determined in “Prerequisites”
on page 38.
3. Click Next.
The Before You Begin page displays prerequisites already discussed in this guide.
SteelFusion Core Installation and Configuration Guide
43
Configuring SteelFusion Core
Configuring the Core with Edges
4. Click Next to display the Specify Portal page.
Figure 3-9. LUN Mapping Wizard - Specify Portal Page
5. Specify the iSCSI portal using the controls described in the following table.
Control
Description
Select from known
Portals
From the IP address drop-down list, select a previously configured iSCSI portal.
Add new Portal
Specify the IP address and port for the intended iSCSI portal.
44
Appliances that appear in this list are independently configured in the Configure >
Storage Array: iSCSI, Initiators, MPIO page.
SteelFusion Core Installation and Configuration Guide
Configuring the Core with Edges
Configuring SteelFusion Core
6. Click Next to display the Manage Targets page.
Figure 3-10. LUN Mapping Wizard - Manage Targets Page
7. Select and add targets from the top panel, which displays the targets discovered on the portal selected
in the previous page.
8. Click Next to display the Mount LUNs page.
Figure 3-11. LUN Mapping Wizard - Mount LUNs Page
SteelFusion Core Installation and Configuration Guide
45
Configuring SteelFusion Core
Configuring the Core with Edges
9. Select and add LUNs from the top panel, which displays the LUNs discovered on the targets selected in
the previous page.
10. Click Next to display the Specify SteelFusion Edge page.
Figure 3-12. Setup Wizard - Specify SteelFusion Edge Page
11. Specify the Edge using the controls described in the following table.
Control
Description
Select from known
SteelFusion Edges
From the SteelFusion Edge Identifier drop-down list, select a previously configured
Edge.
Note: After initial configuration, this setting can be modified in the Configure >
Manage: SteelFusion Edges page in the SteelFusion Core Management Console. You
can also add more Edges.
Add new SteelFusion Edge
Specify the hostname for the intended Edge.
12. Click Next to display the Map LUNs to Edge page.
46
SteelFusion Core Installation and Configuration Guide
Configuring the Core with Edges
Configuring SteelFusion Core
13. Select and map LUNs from the top panel, which displays the unmapped LUNs, to the Edge selected in
one of the preceding pages.
Figure 3-13. LUN Mapping Wizard - Map LUNs to Edge Page
14. Click Next to display the Summary page.
The Summary page displays the settings configured in the LUN settings pages and provides links
directly to the related configuration pages.
15. Click Exit to complete the set-up procedure.
Confirming the Connection to an Edge
This section describes how to confirm that a specific Edge is communicating with the newly configured
Core.
To confirm the connection
1. Return to the SteelFusion Edge Management Console used in “Configuring the Edge” on page 39.
2. Choose Storage > Storage Edge Configuration to display the Storage page.
SteelFusion Core Installation and Configuration Guide
47
Configuring SteelFusion Core
Configuring the Core with Edges
The page display depends on the current device configuration. Figure 3-14 shows the initial page
without any configuration. Figure 3-15 shows an Edge connected to a Core configured with Edge high
availability. If the connection is successful, the page displays connection details including the iSCSI
target configuration and LUN information.
Figure 3-14. SteelFusion Storage Page
Figure 3-15. SteelFusion Storage Page
48
SteelFusion Core Installation and Configuration Guide
Configuring the Core with Edges
Configuring SteelFusion Core
Performing Additional Configuration Settings
After performing the initial setup using the setup wizard, you can configure additional iSCSI initiators and
LUNs, connect to more Edges, configure authentication using Challenge-Handshake Authentication
Protocol (CHAP), and set up storage array snapshots.

Configuring iSCSI settings - You can view and configure the iSCSI initiator, portals, and targets in the
iSCSI Configuration page.
The iSCSI initiator settings configure how the Core communicates with one or more storage arrays
(targets) through the specified portal configuration. After configuring the iSCSI portal, you can open
the portal configuration to configure targets.

Configuring LUNs - You can configure block disk, iSCSI, and Edge Local LUNs in the LUNs page.
Typically, block disk and iSCSI LUNs are used to store production data. They share the space in the
blockstore cache of the associated Edges, and the data is continuously replicated and kept
synchronized with the associated LUN in the data center. The Edge blockstore caches only the working
set of data blocks for these LUNs; additional data is retrieved from the data center when needed.
Edge Local LUNs are used to store transient and temporary data. Local LUNs also use dedicated space
in the blockstore cache of the associated Edges, but the data is not replicated back to the data center
LUNs.

Adding Edges - After you configure the LUNs and Edges for the Core, you can map the LUNs to the
Edges to which they are to be exposed.
You complete this mapping through the Edge configuration in the SteelFusion Core Management
Console by selecting the Edge configuration from the list in the Configure > Manage: SteelFusion
Edges page.

Configuring snapshots - You can implement block level snapshots for specified storage arrays,
configure snapshot schedule policies (which you can be apply to configured LUNs), and configure
hosts for snapshot scripting in the Snapshots page.
For details about the above procedures, see the SteelFusion Core Management Console User’s Guide.
SteelFusion Core Installation and Configuration Guide
49
Configuring SteelFusion Core
50
Configuring the Core with Edges
SteelFusion Core Installation and Configuration Guide
CHAPTER 4
Installing Core-v
This chapter describes how to install and configure Core-v. It includes the following sections:

“Overview of Core-v” on page 51

“Hardware and Software Requirements” on page 52

“Installing and Configuring Core-v for ESX” on page 53

“Obtaining the Core-v VM Image” on page 54

“Gathering Information” on page 54

“Opening the vSphere Client” on page 55

“Logging In to Core-v” on page 56

“Purchasing the Token and Receiving the Licenses” on page 57
Overview of Core-v
Core-v is a virtualized edition of Core that runs on VMware ESX and ESXi 5.0, 5.1, and 5.5. Core-v has the
same functionality and performance as Core, depending on how you provision your virtual machine (VM).
Note: Core-v can run on ESXi 5.5; however, certain features are not supported such as larger LUNs and the SATA driver.
VMware ESX and ESXi are virtualization platforms that enable you to install and run Core-v as a virtual
appliance. For details about VMware ESX and ESXi, see http://www.vmware.com.
The hardware must support virtual technology. To ensure hardware compatibility, see http://
www.vmware.com/resources/compatibility/search.php.
Note: VM snapshots are not supported by SteelHead (virtual edition) for ESX.
SteelFusion Core Installation and Configuration Guide
51
Installing Core-v
Hardware and Software Requirements
Hardware and Software Requirements
This section describes the hardware and software requirements for installing and running Core-v.
Hardware Requirements
It is important to know the number of branches you plan to support before you allocate resources for your
Core-v installation. The following table lists the resources Riverbed recommends for the indicated
maximum number of branches.
Figure 4-1. Hardware Requirements
Model
Memory
Disk Space
Recommended CPU
Data Set Size
Branches
VGC-1000-U
2 GB
25 GB
2 @ 2.2 GHz
2 TB
5
VGC-1000-L
4 GB
25 GB
4 @ 2.2 GHz
5 TB
10
VGC-1000-M
8 GB
25 GB
8 @ 2.2 GHz
10 TB
20
VGC-1500-L
32 GB
350 GB
8 @ 2.2 GHz
20 TB
30
VGC-1500-M
48 GB
350 GB
12 @ 2.2 GHz
35 TB
30
By default, Virtual SteelFusion Core for ESX is configured to support 100 endpoints. To support additional
endpoints, provision appropriately.
Virtual SteelFusion Core for ESX uses hard disk 1 for management and hard disk 2 for stats. When the size
of hard disk 2 is increased to accommodate additional endpoints, Virtual SteelFusion Core resizes hard disk
2 nondestructively. The contents of hard disk 2 are deleted if the size of the disk is decreased.
If you do not allocate memory, data storage, and CPU resources sufficient for the maximum number of
endpoints, 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.
Figure 4-2. Alarm Messages
VM Resource
Alarm Message
Memory
Not enough memory (available = X MB, required = X MB)
Storage
Not enough disk2 storage (available = X MB, required = X MB)
CPU
Not enough cumulative CPU (available = X MHz, required = X MHz)
For example you might receive the following alarm message:
Not enough cumulative CPU (available = 1861.260000 MHz, required = 2000.000000 MHz)
For information on Virtual SteelFusion Core alarms, see the SteelFusion Design Guide.
Recommendations for Optimal Performance
VM configuration is central to Core-v performance. Follow these tips for best results:

52
Use a Gigabit link for the auxiliary interface - For optimal performance, connect the auxiliary virtual
interfaces to physical interfaces that are have a capacity of at least 1 Gbps.
SteelFusion Core Installation and Configuration Guide
Installing and Configuring Core-v for ESX
Installing Core-v

Do not share physical NICs - Assign a physical NIC to a single auxiliary interface. Do not share
physical NICs destined for other virtual interfaces with other VMs running on the ESX host; otherwise,
bottlenecks might result.

Always reserve virtual CPU cycles - For best performance, it is important that Core-v receives
sufficient CPU resources. This resource requirement can be enforced by reserving the number of virtual
CPUs that the model is supposed to function with. Also remember to reserve the number of clock
cycles in terms of CPU MHz; for example, for a model VGC-1000-UL installed on a quad core (Xeonbased system running at 2.6 GHz), you would reserve two vCPUs and 2 x 2.6 GHz CPU cycles using
vSphere.

Do not over-provision the physical CPUs - Do not run more VMs than there are CPUs. For example, if
an ESX host is running on a quad-core CPU, all the VMs on the host should use not more than four
virtual CPUs.

Use a server-grade CPU for the ESX host - Riverbed recommends Xeon or Opteron.

Always reserve RAM - Memory is another very important factor in determining Core-v performance.
For details, see “Hardware Requirements” on page 52.

Do not over-provision physical RAM - The total virtual RAM needed by all running VMs should not
be greater than the physical RAM on the system.

Do not use low-quality storage - Make sure that the Core-v disk used for the Virtual Machine Disk
(VMDK) is located on a physical disk medium that supports a high number of I/O operations per
second (IOPS). For example, use NAS, storage array, or dedicated SATA disks.
Installing and Configuring Core-v for ESX
This section provides an overview of the basic steps to install and configure a Core-v for ESX, followed by
detailed procedures.
Task
Reference
1. Verify your hardware requirements, to ensure
that the hardware you have set aside is sufficient
to run Core-v for ESX.
“Hardware Requirements” on page 52
2. Obtain the Core-v package from Riverbed
Support.
“Obtaining the Core-v VM Image” on page 54
3. Gather network settings for the configuration
wizard.
“Gathering Information” on page 54
4. Deploy the Core-v image.
“Deploying the OVF Template” on page 55
5. Power on the VM, start Core-v, and log in.
“Logging In to Core-v” on page 56
6. Complete the Core-v configuration.
“Logging In to Core-v” on page 56
7. Exit the configuration wizard.
8. Purchase a token from Riverbed Sales.
“Purchasing the Token and Receiving the Licenses” on page 57
9. Refer to the SteelFusion Core Management Console
User’s Guide for configuration specifics and other
Riverbed product documentation for additional
information.
SteelFusion Command-Line Interface Reference Manual
Riverbed Command-Line Interface Reference Manual
SteelFusion Design Guide
SteelFusion Core Installation and Configuration Guide
53
Installing Core-v
Obtaining the Core-v VM Image
Obtaining the Core-v VM Image
Core-v is provided by Riverbed as an image that contains the VMX and VMDK files necessary to create the
VM.
The Core-v image is an installable open virtual appliance (OVA) package. OVA is a platform-independent,
efficient, extensible, and open packaging distribution format. The OVA package provides a complete
specification for Core-v for ESX, including its required virtual disks, CPU, memory, networking, and
storage. The following OVA packages are available:

image.ova for the VGC-1000 series

image-vgc.ova for the VGC-1500 series
Note: Model upgrades from a VGC-1000 series to a VGC-1500 series are not supported through licensing. You must
deploy the correct OVA package.
The OVA file is a compressed .tar package that quickly creates a VM with predefined settings. It contains
the following files:

OVF file - The XML description of Core-v.

VMDK file - This file contains the management system.

Manifest file - The checksum of the OVF and VMDK.

VMX file - The primary configuration that is created when the OVA is deployed.
To obtain the OVA package, log in to your customer account at https://support.riverbed.com.
Gathering Information
Before you begin, read the release notes for the product at https://support.riverbed.com. They contain
important information about this release. Next, gather the following information:

Hostname

Domain name

IP address

DNS server

Interface IP addresses

Netmask

Default gateway
54
SteelFusion Core Installation and Configuration Guide
Opening the vSphere Client
Installing Core-v
Opening the vSphere Client
Each package contains a predefined virtual hardware configuration for a Core-v. Do not open or modify
any of the files in the package. The package files require approximately 25 GB of disk space.
Installation procedures vary depending on whether you are using the VMware VI or vSphere client. The
examples in this document are created using vSphere.
Core-v on ESX is provided by Riverbed as an OVA file on 4.1 and newer systems.
Deploying the OVF Template
This section describes how to install and configure the default Core-v on a VMware ESX host using the
vSphere client.
The standard installation puts both VMDKs in a single local storage location. The local storage holds the
VM files and is referred to as a datastore during OVF deployment, but it is not used for the RiOS datastore,
which is used for network optimization.
Make sure the local storage datastore you select has enough capacity for the OVA package to be installed.
You need at least 25 GB. The larger VMDK containing the management system can be installed on any
datastore type. The smaller VMDK contains the Core-v statistics. The datastore must have enough room to
expand to the required size of the Core-v. Do not share host physical disks (such as SCSI or SATA disks)
between VMs.
To deploy the OVA template
1. Open VMware vSphere, type the hostname IP address or name, type your username and password, and
click Login.
2. Choose File > Deploy OVF template.
3. Click Deploy from file, and then click Browse.
4. Select the OVA file (filename ending in .ova), and click Open.
5. Click Next.
6. Verify that the OVA file is the one you want to deploy.
7. Click Next.
8. Type a name for the VM.
9. Click Next.
10. Select Thick provisioned format unless you have a specific reason for requiring thin provisioning.
11. Click Next.
12. Select the destination network name and select a network from the drop-down list to map the source
network to a destination network. Set Primary to Aux and Aux to Primary.
SteelFusion Core Installation and Configuration Guide
55
Installing Core-v
Logging In to Core-v
13. Click Next.
14. Verify the deployment settings and click Finish.
A message shows the amount of time before the deployment is finished. When the deployment
finishes, a message tells you the deployment was successful. You can edit disk size and provisioning
settings later by right-clicking the name of your VM.
15. Click Close.
The new VM appears under the hostname or host IP address to the VM inventory.
Logging In to Core-v
This section describes how to log in to Core-v.
You can connect to Core-v through any supported web browser. To connect to Core-v you must know the
host, domain, and administrator password that you assigned during the initial setup.
Note: Cookies and JavaScript must be enabled in your browser.
To log in to Core-v
1. Enter the URL for Core-v in the location box of your browser:
<protocol>://<host>.<domain>
Where:
–
<protocol> is http or https. The secure HTTPS uses SSL protocol to ensure a secure environment. If
you use HTTPS to connect, you are prompted to inspect and verify the SSL key.
–
<host> is the IP address or hostname you assigned to Core-v during the initial configuration. If
your DNS server maps the IP address to a name, you can specify the DNS name.
–
<domain> is the full domain name for Core-v.
Core-v interface appears, displaying the Login page.
2. In the Username text box, the default account admin appears.
You must specify the account admin when you first log in.
Optionally, at a later time, you can configure the monitor username, RADIUS users, or TACACS+
users. For detailed information, see the SteelFusion Core Management Console User’s Guide.
3. In the Password text box, type the password you assigned in the Core-v configuration wizard.
4. Click Log In to log in and display the Home page.
56
SteelFusion Core Installation and Configuration Guide
Purchasing the Token and Receiving the Licenses
Installing Core-v
Purchasing the Token and Receiving the Licenses
Before you can add licenses to a Core-v, you must first purchase a token from Riverbed. The token has a
model number assigned to the new Core-v after you complete its licensing. To view your purchased token,
log in to your account at https://support.riverbed.com.
Note: For details about licensing, see “Managing Riverbed Licenses” on page 25.
After you receive a token you are ready to install the licenses.
To activate the token and install the license
1. Log in to Core-v.
2. Choose Settings > Maintenance: Licenses to display the Licenses page.
3. Under License Request, type the token and click Generate License Request Key.
When you enter the token, RiOS returns a license request key.
4. After you have obtained the license request key, go to the Riverbed Licensing Portal at http://
licensing.riverbed.com (nonregistered users) or to the Riverbed Support site at https://
support.riverbed.com/content/support/my_riverbed/tokens.html (registered users) to generate your
license keys.
The license keys include the GCBASE license as well as any other licenses needed for Core-v.
The Licensing Portal is a public website; the Riverbed Support website requires registration.
After your licenses are generated, they appear online and are also emailed to you for reference.
5. Copy and paste the license key into the text box. Separate multiple license keys with a Space, Tab, or
Enter.
6. Click Add License(s).
Core-v status should change to Healthy, indicated in green, a few seconds after you add the GCBASE
and Model GCMSPECV licenses.
7. Click Config Save Required, next to the Healthy status indicator, to save your configuration.
SteelFusion Core Installation and Configuration Guide
57
Installing Core-v
58
Purchasing the Token and Receiving the Licenses
SteelFusion Core Installation and Configuration Guide
APPENDIX A
SteelFusion Core Status Lights,
Ports, and Technical Specifications
This appendix describes the status lights, ports, and the technical and environmental specifications for
SteelFusion Core appliances. It includes the following sections:

“SteelFusion Core 3500 Specifications” on page 59

“SteelFusion Core 3000 Specifications” on page 63

“SteelFusion Core 2000 Specifications” on page 67
For information about NICs for Core, see the Network and Storage Card Installation Guide.
SteelFusion Core 3500 Specifications
This section describes the status lights, ports, and technical and environmental specifications of the
SteelFusion Core 3500 appliance.
SteelFusion Core Installation and Configuration Guide
59
SteelFusion Core Status Lights, Ports, and Technical Specifications
SteelFusion Core 3500 Specifications
Status Lights and Ports
The following figures show the status light and port locations.
Figure A-1.Front Panel
Figure A-2.Back Panel
Note: By default, the SteelFusion Core 3500 ships with a four-port 1G copper network card in slot 1. The default
interface names for this card are ETH1_0, ETH1_1, ETH1_2, and ETH1_3.
60
SteelFusion Core Installation and Configuration Guide
SteelFusion Core 3500 Specifications
SteelFusion Core Status Lights, Ports, and Technical Specifications
The following table summarizes the appliance LEDs and buttons.
Reference
LED/Button
Description
Maintenance = Blue
1
System ID Button with
Integrated LED
Toggles the integrated ID LED and the blue server board ID LED on and
off. The System ID LED identifies the system for maintenance when
installed in a rack of similar server systems. You can also remotely turn
on and turn off the System ID LED using the IPMI “Chassis Identify”
command, which causes the LED to blink for 15 seconds.
A duplicate System ID LED is on the back of the appliance to the left of
the video port.
2
NMI Button
Network Activity LED
3
10
Primary
Auxiliary
Link = Green
Activity = Blinks Green. The blink rate is consistent with the amount of
network activity.
The appliance does not use this LED.
4
5
Pressing the NMI button puts the appliance in a halt state and issues a
nonmaskable interrupt (NMI). This process helps when performing
diagnostics for a given issue where a memory download is necessary to
determine the cause of the problem. To prevent an inadvertent system
halt, the NMI button is located behind the Front Control Panel faceplate
and is only accessible with the use of a small tipped tool such as a pin or
paper clip.
System Cold Reset Button
Pressing this button reboots the appliance.
The System Status LED shows the current health of the server system.
6
System Status LED
Healthy = Green
Degraded = Yellow
Critical = Blinks Yellow
7
Power Button with
Integrated LED
System On = Green
System Off = No Light
8
Drive Activity
Activity = Blinks Green
The appliance does not use this LED.
9
Activity LED
Read/Write Activity = Blinks Green
LEDs on Disk Drives
LEDs on Primary and AUX
Ports
LEDs on Power Supply
Disk Fault LED
Failed Disk = Orange
RAID Rebuild = Blinks Orange
Left LED
Link = Green
Activity = Blinks Green
Right LED
10 MBps data rate = No Light (with link on left LED)
100 MBps data rate = Green
1000 MBps data rate = Yellow
Power On and Healthy = Green
Power Off = Off
Standby = Blinks Green
Power Lost But Second Power Supply Has Power = Amber
Power On With Warning Events (high temperature, high power, high
current, slow fan) = Blinks Amber
SteelFusion Core Installation and Configuration Guide
61
SteelFusion Core Status Lights, Ports, and Technical Specifications
SteelFusion Core 3500 Specifications
Technical Specifications
The following table summarizes the technical specifications for the systems.
SFCR3500
Form Factor
2U
Hard Disk/SSD
4 x 1000 GB HDD
2 x 80 GB SSD
Dimensions (LxWxH)
27.87 x 17.24 x 3.45 in.
708 x 438 x 88 mm
Weight (without packaging)
42 lb/19.05 kg
Voltage Frequency
100–127 V – 200–240 V
PSU
2x
770 W
100–127 VAC/8.2 A, 50/60 Hz
200–240 VAC/4.4 A, 50/60 Hz
PCI Slots
6
Included Ports/Max # Ports
6/26
Power Requirements and Consumption
The following table summarizes the power specifications for the systems. The systems are rated at the
following power characteristics when operating at nominal AC input voltages (120 V and 230 V).
System
SFCR3500
SFCR3500
Configuration
All
All
PSU Type
2 x 770 W
2 x 770 W
AC Input
120 V
230 V
Max. Amps.
3.12
1.5
Max. Watts
310
302
Typical Watts
248
242
Max VA
313
305
Power Factor
98.96
99.16
BTU (Typical)
845
825
62
SteelFusion Core Installation and Configuration Guide
SteelFusion Core 3000 Specifications
SteelFusion Core Status Lights, Ports, and Technical Specifications
Environmental Specifications
The following table summarizes the environmental requirements for the systems.
SFCR3500
Operating
Acoustic
7.0 BA Sound Pressure (Typical)
Temperature
(Operating)
10º–35ºC
50°–95ºF
Temperature
(Storage)
-40º–70ºC
-40º–158ºF
Relative
Humidity
50% to 90%, noncondensing with a maximum
wet bulb of 28ºC (at temperatures from 25 to
35ºC)
RAM Sizing
The following table lists the memory and processing sizing requirements based on data set size and the
number of LUNs served by the data center in which Core is deployed.
Size
Configuration
Maximum RAM
CPU
Cores
Data Set Size
LUNs
2U
SFCR3500C1
256 GB
12
25 TB
150
2U
SFCR3500C2
256 GB
12
50 TB
200
2U
SFCR3500C3
256 GB
12
100 TB
300
SteelFusion Core 3000 Specifications
This section describes the status lights, ports, technical and environmental specifications of the SteelFusion
Core 3000 appliance.
SteelFusion Core Installation and Configuration Guide
63
SteelFusion Core Status Lights, Ports, and Technical Specifications
SteelFusion Core 3000 Specifications
Status Lights and Ports
The following figures show the status light and port locations.
Figure A-3.Front Panel
Figure A-4.Back Panel
The following table summarizes the system LEDs.
LED
Status
SYSTEM
Normal = Blue
System Boot = Red
PRI = Primary
AUX = Auxiliary
REM = Remote
Link and Traffic = Blinks Blue
ETH
Link and Traffic = Blinks Blue
HDDs/SSDs
Disk Connected = Blue
Read/Write Activity = Blinks Blue
Failed Disk = Orange
Back Panel
ETH0_0, ETH0_1
64
Left LED
Link = Green
Activity = Blinks Green
Right LED
GB = Orange
100 MB = Green
10 MB = No Light
SteelFusion Core Installation and Configuration Guide
SteelFusion Core 3000 Specifications
SteelFusion Core Status Lights, Ports, and Technical Specifications
Technical Specifications
The following table summarizes the technical specifications for the system.
SFCR3000
2U
L-M-H
Power Amps
400 W
VA (max)
415 VA
BTU
1368 BTU
HDD/SSD
2 x 1 TB 2.5 in.
Dimensions (L x W x H)
17.56 x 25.37 x 3.42 in.
446 x 644 x 88 mm
Weight (without packaging)
58 lb (26.31 kg)
Voltage
100–127 VAC/8 A, 50/60 Hz
200–240 VAC/4 A, 50/60 Hz
PSU
2 x 770 W
PCIe Slots
4
Power Requirements and Consumption
The following table summarizes the power specifications for the system. The system is rated at the
following power characteristics when operating at nominal AC input voltage (230 V).
SteelFusion Core Installation and Configuration Guide
65
SteelFusion Core Status Lights, Ports, and Technical Specifications
System
SFCR3000
Configuration
All (L-M-H)
PSU Type
2 x 770W
AC Input
230 V
Max. Amps.
3.2
Max. Watts
430
Typical Watts
400
Max. VA
515
Power Factor
94
BTU (Typical)
1368
SteelFusion Core 3000 Specifications
Environmental Specifications
The following table summarizes the environmental specifications for the systems.
SFCR3000
2U
L-M-H
Operating
Acoustic
65.5 dBa Sound Pressure
(Typical)
Temperature
(Operating)
50°–104ºF (10º–40ºC)
Temperature
(Storage)
-40º–149ºF (-40º–65ºC)
Relative
Humidity
20–80%
noncondensing
Storage
Humidity
5–95%
noncondensing
Operating
Altitude
-50–10,000 ft (-15.24–3048 m)
RAM Sizing
The following table describes the memory and processing sizing requirements based on data set size and
the number of LUNs served by the data center in which Core is deployed.
Size
Model
Maximum RAM
Cores
Data Set Size
LUNs
2U
SFCR3000L
128 GB
16
50 TB
200
2U
SFCR3000M
128 GB
16
75 TB
250
2U
SFCR3000H
128 GB
16
100 TB
300
66
SteelFusion Core Installation and Configuration Guide
SteelFusion Core 2000 Specifications
SteelFusion Core Status Lights, Ports, and Technical Specifications
SteelFusion Core 2000 Specifications
This section describes the status lights, ports, and technical and environmental specifications of the
SteelFusion Core 2000 appliance.
Status Lights and Ports
The following figures show the status light and port locations.
Figure A-5.Front Panel
Figure A-6.Back Panel
The following table summarizes the system LEDs.
LED
Status
SYSTEM
Normal = Blue
System Boot = Red
PRI = Primary
AUX = Auxiliary
REM = Remote
Link and Traffic = Blinks Blue
ETH
Link and Traffic = Blinks Blue
SteelFusion Core Installation and Configuration Guide
67
SteelFusion Core Status Lights, Ports, and Technical Specifications
SteelFusion Core 2000 Specifications
LED
Status
BYP/BLK
BYP = Bypass
BLK = Block (Disconnect)
Normal = No Light
Bypass or Block (Disconnect) = Orange
HDDs/SSDs
Disk Connected = Blue
Read/Write Activity = Blinks Blue
Failed Disk = Orange
Back Panel
ETH0_0, ETH0_1
Left LED
Link = Green
Activity = Blinks Green
Right LED
GB = Orange
100 MB = Green
10 MB = No Light
Technical Specifications
The following table summarizes the technical specifications for the system.
SFCR2000
2U
L-M-H-VH
Power Amps
355 W
VA (max)
415 VA
BTU
1215 BTU
HDD
2 x 500 GB 3.5 in.
Dimensions (L x W x H)
17.56 x 25.37 x 3.42 in.
446 x 644 x 87 mm
Weight (without packaging)
58 lb (23.31 kg)
Voltage
100–127 VAC/8 A, 50/60 Hz
200–240 VAC/4 A, 50/60 Hz
PSU
2 x 770 W
PCIe Slots
4
Power Requirements and Consumption
The following table summarizes the power specifications for the system. The system is rated at the
following power characteristics when operating at nominal AC input voltage (230 V).
68
SteelFusion Core Installation and Configuration Guide
SteelFusion Core 2000 Specifications
System
SFCR2000
Configuration
All (L/M/H/VH)
PSU Type
2 x 770 W
AC Input
230 V
Max. Amps.
3.2
Max. Watts
430
Typical Watts
345
Max. VA
515
Power Factor
94
BTU (Typical)
1175
SteelFusion Core Status Lights, Ports, and Technical Specifications
Environmental Specifications
The following table summarizes the environmental specifications for the systems.
SFCR2000
2U
L-M-H-VH
Operating
Acoustic
65.5 dBa Sound Pressure
(Typical)
Temperature
(Operating)
50º–104ºF (10º–40ºC)
Temperature
(Storage)
-40º–149ºF (-40º–65ºC)
Relative
Humidity
20–80%
noncondensing
Storage
Humidity
5–95%
noncondensing
Operating
Altitude
-50–10,000 ft. (-15.24–3048 m)
RAM Sizing
The following table lists the memory and processing sizing requirements based on data set size and the
number of LUNs served by the data center in which Core is deployed.
Size
Model
Maximum RAM
Cores
Data Set Size
LUNs
2U
SFCR2000L
24 GB
4
5 TB
20
2U
SFCR2000M
24 GB
4
10 TB
40
SteelFusion Core Installation and Configuration Guide
69
SteelFusion Core Status Lights, Ports, and Technical Specifications
SteelFusion Core 2000 Specifications
Size
Model
Maximum RAM
Cores
Data Set Size
LUNs
2U
SFCR2000H
24 GB
4
20 TB
80
2U
SFCR2000VH
24 GB
4
35 TB
160
70
SteelFusion Core Installation and Configuration Guide
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising