SteelHead Interceptor Appliance Installation Guide Version 5.0 July 2015
2015 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-00021-13
Contents Preface...1 About This Guide...1 Audience...1 Document Conventions...2 Documentation and Release Notes...2 Contacting Riverbed...3 Chapter 1 - Overview of the SteelHead Interceptor...5 Overview of the SteelHead Interceptor...5 Product Dependencies and Compatibility...9 Software Dependencies...10 SteelHead Compatibility...10 Ethernet Network Compatibility...10 SNMP-Based Management Compatibility...11 Safety Guidelines...11 SteelHead Interceptor Deployment Features...11 Deployment Scenarios...12 Deploying Single SteelHead Interceptors...13 Deploying Serial SteelHead Interceptors...14 Deploying Parallel SteelHead Interceptors...14 Deploying Quad SteelHead Interceptors...15 New Features in Version 5.0...16 Upgrading to Version 5.0...16 Chapter 2 - Installing the SteelHead Interceptor...19 Choosing a Deployment Design...19 LAN-Side Versus WAN-Side SteelHead...20 Layer-2 Versus Layer-3 Connectivity...20 Multiple SteelHead Link Support...20 Multiple SteelHead Support...20 SteelHead Interceptor Appliance Installation Guide iii
Contents Checking Your Inventory...21 Preparing Your Site for Installation...21 Site Requirements...21 Preparing for Registration with the SteelCentral Controller for SteelHead...22 Registering the SteelHead Interceptor with the SCC...22 Completing the Configuration Checklist...23 Powering On the System...24 Running the Configuration Wizard...24 Configuring In-Path SteelHeads...27 Connecting In-Path SteelHeads to Your Network...27 Verifying Your Connections...31 Next Steps...31 Appendix A - Technical Specifications...33 SteelHead Interceptor 9600 Specifications...33 Status Lights and Ports...34 Technical Specifications...36 Power Requirements and Consumption...37 Environmental Specifications...37 SteelHead Interceptor 9350 Specifications...37 Status Lights and Ports...37 SteelHead Interceptor Status Beeps...39 Technical Specifications...39 Index...41 iv SteelHead Interceptor Appliance Installation Guide
Preface Read this preface for an overview of the information provided in this guide. This preface includes the following sections: About This Guide on page 1 Documentation and Release Notes on page 2 Contacting Riverbed on page 3 About This Guide The SteelHead Interceptor Appliance Installation Guide provides an overview of SteelHead Interceptor features, specifications, terminology, and deployment scenarios. This document also describes how to install and connect a SteelHead Interceptor to your network. For complete details on SteelHead Interceptor deployment scenarios, see the SteelHead Interceptor Deployment Guide. Riverbed product names have changed. At the time of publication, the user interfaces of the products described in this guide may have not changed, and the original names may be used in the text. For the product naming key, see http://www.riverbed.com/products/#product_list. This guide includes information relevant to the following products: Riverbed Optimization System (RiOS) Riverbed SteelHead (SteelHead) Riverbed SteelHead CX (SteelHead CX) Riverbed SteelHead EX (SteelHead EX) Audience This guide is written for storage and network administrators familiar with administering and managing WANs using common network protocols such as TCP, CIFS, HTTP, FTP, and NFS. You must also be familiar with administering and managing a network of deployed SteelHeads as described in the SteelHead Installation and Configuration Guide. SteelHead Interceptor Appliance Installation Guide 1
Preface Documentation and Release Notes Document Conventions This guide uses the following standard set of typographical conventions. Convention Meaning italics boldface Courier Within text, new terms and emphasized words appear in italic typeface. Within text, CLI commands, CLI parameters, and REST API properties appear in bold typeface. 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. 2 SteelHead Interceptor Appliance Installation Guide
Contacting Riverbed Preface 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. SteelHead Interceptor Appliance Installation Guide 3
Preface Contacting Riverbed 4 SteelHead Interceptor Appliance Installation Guide
CHAPTER 1 Overview of the SteelHead Interceptor This chapter introduces the SteelHead Interceptor. It includes the following sections: Overview of the SteelHead Interceptor on page 5 Product Dependencies and Compatibility on page 9 Safety Guidelines on page 11 SteelHead Interceptor Deployment Features on page 11 Deployment Scenarios on page 12 New Features in Version 5.0 on page 16 Upgrading to Version 5.0 on page 16 Overview of the SteelHead Interceptor The SteelHead Interceptor enables you to scale your deployments of SteelHeads at large central sites. Deployed in-path, SteelHead Interceptors provide virtual in-path clustering and load balancing for SteelHeads that are physically deployed out-of-path. The SteelHead Interceptor is typically deployed in a data center or hub network where any in-path devices need to be high performing and highly available. The SteelHead Interceptor directs incoming traffic to its clustered SteelHeads according to in-path, service, and load-balancing rules. The SteelHead Interceptor is an in-path clustering solution you can use to distribute optimized traffic to a local group of SteelHeads. The SteelHead Interceptor does not perform optimization itself. Therefore, you can use it in demanding network environments with extremely high throughput requirements. The SteelHead Interceptor works in conjunction with the SteelHead and offers several benefits over other clustering techniques, such as Web Cache Communication Protocol (WCCP) or Layer-4 switching, including native support for asymmetrically routed traffic flows. Note: For details on in-path, service, and load-balancing rules, see the SteelHead Interceptor User s Guide. SteelHead Interceptor Appliance Installation Guide 5
Overview of the SteelHead Interceptor Overview of the SteelHead Interceptor The SteelHead Interceptor includes the following features: Feature Connection Tracing Description Connection traces enable you to identify the SteelHeads to which the SteelHead Interceptor has forwarded specific connections. Connection traces also enable users to debug failing or unoptimized connections or failing pass-through path-selection connections (if the Path Selection feature is enabled). Note: For details on setting connection tracing, see the SteelHead Interceptor User s Guide. EtherChannel Deployment Failover The SteelHead Interceptor can operate within an EtherChannel deployment. In an EtherChannel deployment, all the links in the channel must pass through the same SteelHead Interceptor. These two configurations are supported: up to four channels with two links per channel group, or up to two channels with four links per channel group. You can configure a pair of SteelHead Interceptors for failover. In the event that one SteelHead Interceptor goes down or requires maintenance, the second SteelHead Interceptor configured for failover ensures uninterrupted service. Note: For details on setting failover, see the SteelHead Interceptor User s Guide. You can configure a SteelHead Interceptor 9350 as the failover appliance for a SteelHead Interceptor 9600 if you enable the 9350-mode on the SteelHead Interceptor 9600. The 9350-mode is enabled by using the appliance operating-mode 9350 command. Note: For more information about the appliance operating-mode 9350 command, see the Riverbed Command-Line Interface Reference Manual. 6 SteelHead Interceptor Appliance Installation Guide
Overview of the SteelHead Interceptor Overview of the SteelHead Interceptor Feature In-Path Rules Description When the SteelHead Interceptor intercepts a SYN request to a server, the in-path rules you configure determine the subnets and ports for traffic to be optimized. You can specify in-path rules to pass through, discard, deny traffic, or to forward and optimize it. In the case of a data center, the SteelHead Interceptor intercepts SYN requests when a data center server establishes a connection with a client that resides outside of the data center. In the connection-processing decision tree, in-path rules are processed before loadbalancing rules. Only traffic selected for forwarding proceeds to load-balancing rules processing. Traffic selected for pass-through proceeds to service rule processing if Path Selection is enabled. Note: For details on setting in-path rules and Path Selection, see the SteelHead Interceptor User s Guide. Intelligent Forwarding Interceptor Monitoring Link State Detection and Link State Propagation Intelligent Forwarding prevents the SteelHead Interceptor from forwarding the same packet to the SteelHead more than once. This feature prevents loops in case the packet that was already processed is routed through the SteelHead Interceptor again. Cluster SteelHead Interceptors include both failover pairs deployed in a serial configuration and SteelHead Interceptors deployed in a parallel configuration to handle asymmetric routes. Asymmetric routing can cause the response from the server to be routed along a different physical network path from the original request, and a different SteelHead Interceptor can be on each of these paths. When you deploy SteelHead Interceptors in parallel, the first SteelHead Interceptor that receives a packet forwards the packets to the appropriate SteelHead. The SteelHead Interceptor monitors the link state of devices in its path, including routers, switches, interfaces, and in-path interfaces. When the link state changes for a device that is part of a bridge, the link state change is propagated to the other devices on the bridge as well. SteelHead Interceptor Appliance Installation Guide 7
Overview of the SteelHead Interceptor Overview of the SteelHead Interceptor Feature Load-Balancing Rules Description For connections selected by an in-path redirect rule, the SteelHead Interceptor distributes the connection to the most appropriate SteelHead based on rules you configure, intelligence from monitoring cluster SteelHeads, and the RiOS connection distribution algorithm. The SteelHead Interceptor combines two approaches to load balancing: Peer affinity - The SteelHead Interceptor sends the connection to the local SteelHead with the most affinity (that is, the local SteelHead that has received the greatest number of connections from the remote SteelHead). Round-robin distribution - Instead of checking the SteelHeads in order of most to least peer affinity, the SteelHeads are checked for availability in round-robin order starting with the one after the SteelHead that received the last connection from that rule. Note: Round-robin distribution can be enabled using the CLI only. It cannot be configured using the GUI. Note: For details on setting load-balancing rules (including information on Fair Peering V2 as it relates to load balancing), see the SteelHead Interceptor User s Guide. Peer Affinity Peer affinity refers to an established connection relationship between remote and cluster SteelHeads. Affinity-based load balancing matches traffic from a remote SteelHead to a specific cluster SteelHead based on a previous connection between them. Note: If no local SteelHead is currently handling the remote SteelHead, then the SteelHead Interceptor directs the traffic to the SteelHead with the lowest connection count. If the SteelHead with the best peer affinity is unavailable, the SteelHead Interceptor attempts to use the SteelHead with the next best affinity. Port Labels Path Selection Port labels enable you to apply rules to a range of ports. The SteelHead Interceptor provides port labels for secure and interactive ports, and for Riverbed Technology (RBT) ports. You can create additional labels as needed. RiOS v9.1.0 and later extends path selection to operate in SteelHead Interceptor cluster deployments, providing high-scale and high-availability deployment options. A SteelHead Interceptor cluster is one or more SteelHead Interceptors collaborating with one or more SteelHead appliances to select paths dynamically in complex architectures working together as a single solution. You can configure service rules to specify whether UDP traffic flows should be subject to path selection (that is, redirected to a SteelHead appliance or relayed without being path selected). Note: For details on enabling path selection and configuring service rules, see the SteelHead Interceptor User s Guide. Reporting The SteelHead Interceptor reporting function allows you to generate interface counter reports, diagnostic reports (to check CPU utilization, memory paging, and system logs), and export data. 8 SteelHead Interceptor Appliance Installation Guide
Product Dependencies and Compatibility Overview of the SteelHead Interceptor Feature SteelHead Monitoring System Status VLAN Tagging Description Cluster SteelHeads are the pool of SteelHeads for which the SteelHead Interceptor monitors capacity and balances load. To assist in deployment tuning and troubleshooting, the SteelHead Interceptor can monitor SteelHeads for connectivity, health, and load balancing (if Pressure Monitoring is enabled). The Dashboard displays system status information such as the system uptime, service uptime, SteelHead Interceptors, and SteelHead connections. The SteelHead Interceptor supports VLAN tagged connections in VLAN trunked links. The SteelHead Interceptor supports VLAN 802.1q. Note: The SteelHead Interceptor does not support the Cisco InterSwitch Link (ISL) protocol. Product Dependencies and Compatibility This section provides information about product dependencies and compatibility. It includes the following sections: Software Dependencies on page 10 SteelHead Compatibility on page 10 Ethernet Network Compatibility on page 10 SNMP-Based Management Compatibility on page 11 Safety Guidelines on page 11 SteelHead Interceptor Appliance Installation Guide 9
Overview of the SteelHead Interceptor Product Dependencies and Compatibility Software Dependencies The following table summarizes the software requirements for the SteelHead Interceptor. Riverbed CLI Hardware Requirements One of the following: An ASCII terminal or emulator that can connect to the serial console (9600 baud, 8 bits, no parity, 1 stop bit, and no flow control) A computer with a Secure Shell (ssh) client that is connected by an IP network to the appliance primary interface Software and Operating System Requirements Secure Shell (ssh). Free ssh clients include PuTTY for Windows computers, OpenSSH for many UNIX and UNIX-like operating systems, and Cygwin. Riverbed Component Interceptor Management Console Software Requirements Any computer that supports a Web browser with a color image display. The Management Console has been tested with Mozilla Firefox v10.0 and Microsoft Internet Explorer v7.0 and v8.0. JavaScript and cookies must be enabled in your Web browser. SteelHead Compatibility The SteelHead Interceptor with VLAN segregation enabled is fully compatible with SteelHead version 8.0.1 and supports up to 24 total interfaces in SteelHead versions 6.5.6 and later. Ethernet Network Compatibility The SteelHead Interceptor supports the following Ethernet networking standards: Ethernet Logical Link Control (LLC) (IEEE 802.2-1998) Fast Ethernet 100 Base-TX (IEEE 802.3-2008) Gigabit Ethernet over Copper 1000 Base-T and Fiber 1000 Base-SX (LC connector) and Fiber 1000 Base- LX (IEEE 802.3-2008) 10 Gigabit Ethernet over Fiber 10GBase-LR Single Mode and 10GBase-SR Multimode (IEEE 802.3-2008) The SteelHead Interceptor ports support the following connection types and speeds: Primary - 10/100/1000 Base-T, autonegotiating Auxiliary - 10/100/1000 Base-T, autonegotiating LAN - 10/100/1000 Base-TX or 1000 Base-SX or 1000 Base-LX or 10GBase-LR or 10GBase-SR, depending on configuration WAN - 10/100/1000 Base-TX or 1000 Base-SX or 1000 Base-LX or 10GBase-LR or 10GBase-SR, depending on configuration The SteelHead Interceptor supports VLAN Tagging (IEEE 802.1Q - 2005). It does not support the ISL protocol. All copper interfaces are autosensing for speed and duplex (IEEE 802.3-2008). 10 SteelHead Interceptor Appliance Installation Guide
Safety Guidelines Overview of the SteelHead Interceptor The SteelHead Interceptor autonegotiates speed and duplex mode for all data rates and supports full duplex mode and flow control (IEEE 802.3 2008). The SteelHead Interceptor with a Gigabit Ethernet card supports jumbo frames on in-path and primary ports. SNMP-Based Management Compatibility The SteelHead Interceptor 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 only be accessible through SNMPv2 and SNMPv3. SNMP support enables the SteelHead Interceptor to be integrated into network management systems such as Hewlett-Packard OpenView Network Node Manager, BMC Patrol, and other SNMP-based network management tools. Safety Guidelines Follow the safety precautions outlined in the Safety and Compliance Guide when installing and setting up your equipment. Caution: 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. 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. The guide contains the safety information in your national language. Before you install, operate, or service Riverbed products, you must be familiar with the safety information associated with them. Refer to the Safety and Compliance Guide if you do not clearly understand the safety information provided in the product documentation. SteelHead Interceptor Deployment Features This section describes the SteelHead Interceptor features used in SteelHead Interceptor deployments. The feature configurations vary depending on the deployment, as described in the following table. SteelHead Interceptor Appliance Installation Guide 11
Overview of the SteelHead Interceptor Deployment Scenarios Feature Allow failure Cluster SteelHead Interceptor Fail-to-block Fail-to-wire (bypass) Failover Description Allow failure ensures optimized traffic. When contact between two designated SteelHead Interceptors is lost, the remaining SteelHead Interceptor keeps forwarding connections to ensure that optimization continues. In a parallel configuration, consider enabling this feature if no asymmetric routing is expected in the network. Also note that in a parallel configuration using Path Selection, passthrough traffic will not be able to use path selection if the SteelHead Interceptor is disconnected. In a serial configuration, redundancy is provided by default. This feature is configured in the Networking > Network Services: In-Path Interfaces page. For details, see the SteelHead Interceptor User s Guide. When this feature is enabled, SteelHead Interceptors notify each other when they intercept specific packets. For example, during a connection setup phase, when SteelHead Interceptor A receives a SYN packet, it notifies SteelHead Interceptor B, so that when SteelHead Interceptor B sees the SYN/ACK, it forwards it to the appropriate SteelHead. (During the data phase, both SteelHead Interceptors pass subsequent connections directly to the appropriate SteelHeads.) When fail-to-block is enabled, a failed SteelHead Interceptor blocks any network traffic on its path, as opposed to passing it through. In a parallel configuration, fail-to-block should be enabled to force all traffic through a cluster SteelHead Interceptor, thereby enabling optimization to continue. This feature is configured in the Networking > Networking: In-Path Interfaces page. For details, see the SteelHead Interceptor User s Guide. When fail-to-wire (bypass) is enabled, a failed SteelHead Interceptor passes through network traffic. In a serial or quad configuration, fail-to-wire should be enabled to pass all traffic through to the cluster or failover SteelHead Interceptor, thereby enabling optimization to continue. This feature is configured in the Networking > Networking: In-Path Interfaces page. For details, see the SteelHead Interceptor User s Guide. Failover enables you to specify a failover counterpart. When failover is configured, a failover SteelHead Interceptor takes over for a failed SteelHead Interceptor. In a serial configuration, you configure the serial SteelHead Interceptors for mutual failover. For details, see the SteelHead Interceptor User s Guide. Deployment Scenarios You can deploy the SteelHead Interceptor using different deployment scenarios. Typical SteelHead Interceptor deployments have multiple SteelHead Interceptors and SteelHeads, and usually all appliances have more than one enabled and configured in-path interface. For more details, see the SteelHead Interceptor Deployment Guide. You can configure the SteelHead Interceptor to be either a serially connected failover SteelHead Interceptor acting as a backup for the same network paths, or a SteelHead Interceptor cluster that covers different network paths or is used in a virtual in-path cluster. 12 SteelHead Interceptor Appliance Installation Guide
Deployment Scenarios Overview of the SteelHead Interceptor The SteelHead Interceptor relationships and failure reaction features are typically combined in several ways for actual SteelHead Interceptor deployments. You can deploy SteelHead Interceptor clusters in the following ways: Deploying Single SteelHead Interceptors on page 13 Deploying Serial SteelHead Interceptors on page 14 Deploying Parallel SteelHead Interceptors on page 14 Deploying Quad SteelHead Interceptors on page 15 For more details, see the SteelHead Interceptor Deployment Guide. Deploying Single SteelHead Interceptors Figure 1-1 shows a basic single SteelHead Interceptor deployment. Caution: To enable full transparency, do not position any router that might generate ICMP fragmentation needed or forward messages between the SteelHead Interceptor and SteelHeads. Such messages, if not routed through the SteelHead Interceptor, are not received by the SteelHeads, resulting in a possible connection failure. Figure 1-1. Basic Single SteelHead Interceptor Deployment In this deployment, the following elements apply: SteelHead Interceptor - This deployment features one SteelHead Interceptor. Cluster SteelHeads - This deployment features two SteelHeads. SteelHead Interceptor Appliance Installation Guide 13
Overview of the SteelHead Interceptor Deployment Scenarios Deploying Serial SteelHead Interceptors Figure 1-2 shows a fail-to-wire dual-connected SteelHead deployment. Figure 1-2. Serial SteelHead Interceptors, Fail-to-Wire Dual-Connected SteelHeads In this deployment, the following element applies: Fail-to-wire - If either SteelHead Interceptor fails, traffic passes through to the other SteelHead Interceptor. Failure Handling In Figure 1-2, each in-line SteelHead Interceptor is configured for mutual failover to ensure high availability. If either SteelHead Interceptor fails, the other appliance directs all network traffic. Deploying Parallel SteelHead Interceptors Figure 1-3 shows parallel SteelHead Interceptors deployment. Figure 1-3. Parallel SteelHead Interceptors, Fail-to-Block with Dual-Connected SteelHeads In this deployment, the following elements apply: 14 SteelHead Interceptor Appliance Installation Guide
Deployment Scenarios Overview of the SteelHead Interceptor Fail-to-block - This feature is enabled. If either SteelHead Interceptor fails or it blocks traffic, the network automatically reroutes traffic through the remaining SteelHead Interceptor. Connection-forwarding counterpart - This feature is enabled when the SteelHead Interceptors can notify each other about intercepted connections. Allow failure - This feature is optional (but recommended as a best practice). If contact is lost between the cluster SteelHead Interceptors, the remaining SteelHead Interceptor continues directing all connections, ensuring that optimization continues. Failure Handling In Figure 1-3, if a SteelHead Interceptor fails, fail-to-block causes connections to route through the other SteelHead Interceptor, thereby allowing optimization to continue. However, delays might result from traffic reconvergence. Note: The topology shown in Figure 1-3 requires enabling the allow failure feature. Deploying Quad SteelHead Interceptors Figure 1-4 shows quad SteelHead Interceptor deployment. Figure 1-4. Quad SteelHead Interceptors with Dual-Connected SteelHeads In this deployment, the following elements apply: SteelHead Interceptor Appliance Installation Guide 15
Overview of the SteelHead Interceptor New Features in Version 5.0 Failover Appliance - Each in-line SteelHead Interceptor is configured to provide failover support for the other. Fail-to-Wire - If either in-line SteelHead Interceptor fails, traffic passes through to the other SteelHead Interceptor. Clusters - This feature is enabled where clustered SteelHead Interceptors can notify each other about intercepted connections. Failure Scenarios In Figure 1-4, each parallel network uses two in-line SteelHead Interceptors. Each in-line SteelHead Interceptor is configured as fail-to-wire, so if one fails, network traffic passes through to its in-line counterpart, which is configured for failover. This scenario is distinct from the parallel network configuration shown in Deploying Parallel SteelHead Interceptors on page 14 because the in-line redundancy eliminates the need for fail-to-block and allow failure configurations. New Features in Version 5.0 The following features are available in the SteelHead Interceptor v5.0: Path Selection with SteelHead Interceptor appliance clusters - RiOS v9.1.0 and later extends path selection to operate in SteelHead Interceptor cluster deployments, providing high-scale and highavailability deployment options. A SteelHead Interceptor cluster is one or more SteelHead Interceptors collaborating with one or more SteelHead appliances to select paths dynamically in complex architectures working together as a single solution. New Dashboard - Version 5.0 includes a new dashboard that contains announcements, system status, a list of SteelHeads, SteelHead Interceptors, and the number of optimized connections per SteelHead. The Dashboard provides access to new tabs: Networking, Optimization, Reports, Administration, and Help. Note: SteelHead Interceptor 5.0 supports the following SteelHead features: QoS marking, SteelFlow, and NetFlow. See the SteelHead Management Console User s Guide for complete feature information. Upgrading to Version 5.0 This section describes how to upgrade to SteelHead Interceptor v5.0. To upgrade SteelHead Interceptor software 1. Download the software image from Riverbed Support to a location such as your desktop. 2. Log in to the SteelHead Interceptor appliance using the Administrator account (admin). 16 SteelHead Interceptor Appliance Installation Guide
Upgrading to Version 5.0 Overview of the SteelHead Interceptor 3. Choose Administration > Maintenance: Software Upgrade page to display the Software Upgrade page. Figure 1-5. Software Upgrade Page 4. Under Install Upgrade, choose one of the following options: From URL - Type the URL that points to the software image that you want to upgrade to. Installing directly from https://support.riverbed.com is not supported. From Riverbed Support Site - Select this option to upgrade from the support site. But before you can do that, check the Support page to ensure that Riverbed Support credentials have been set. From Local File - Browse to your file system and select the software image. Schedule Upgrade for Later - Type the date and time using the following format: yyyy/mm/dd hh:mm:ss. Click Install to upgrade your SteelHead Interceptor software. 5. Choose Administration > Maintenance: Reboot/Shutdown to display the Reboot/Shutdown page. Figure 1-6. Reboot/Shutdown Page 6. Click Reboot to restart the SteelHead Interceptor. To view software version history Under Software Version History on the Software Upgrade page, view the history. SteelHead Interceptor Appliance Installation Guide 17
Overview of the SteelHead Interceptor Upgrading to Version 5.0 18 SteelHead Interceptor Appliance Installation Guide
CHAPTER 2 Installing the SteelHead Interceptor This chapter describes how to install and configure the SteelHead Interceptor. This chapter includes the following sections: Choosing a Deployment Design on page 19 Checking Your Inventory on page 21 Preparing Your Site for Installation on page 21 Preparing for Registration with the SteelCentral Controller for SteelHead on page 22 Completing the Configuration Checklist on page 23 Powering On the System on page 24 Running the Configuration Wizard on page 24 Configuring In-Path SteelHeads on page 27 Verifying Your Connections on page 31 Next Steps on page 31 Caution: 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. Choosing a Deployment Design You can use multiple SteelHead Interceptors to ensure that optimization occurs even when there are multiple, physically separated paths to the WAN, or to ensure that optimization continues during a planned or unplanned SteelHead Interceptor outage. Use multiple SteelHeads to ensure redundancy or to specify that certain applications, subnets, and hosts are optimized by different SteelHeads. For more details on deployment scenarios, see the SteelHead Interceptor Deployment Guide. This section describes the following deployment designs: LAN-Side Versus WAN-Side SteelHead on page 20 Layer-2 Versus Layer-3 Connectivity on page 20 Multiple SteelHead Link Support on page 20 SteelHead Interceptor Appliance Installation Guide 19
Installing the SteelHead Interceptor Choosing a Deployment Design Multiple SteelHead Support on page 20 LAN-Side Versus WAN-Side SteelHead You connect SteelHeads to the local network on either the LAN or WAN side of the SteelHead Interceptor. For most deployments, LAN-side SteelHead placement minimizes the amount of traffic that traverses the SteelHead Interceptor. LAN-side SteelHead placement is, therefore, the recommended choice. You cannot cable the SteelHead directly to the SteelHead Interceptor. For more details, see the SteelHead Interceptor Deployment Guide. Layer-2 Versus Layer-3 Connectivity The SteelHead and SteelHead Interceptor in-path IP addresses can be on the same, or different subnets. The actions taken to redirect traffic are the same during autodiscovery and optimization. Unlike when you use WCCP to redirect traffic to a SteelHead, there is no resource use or MTU concerns from having the SteelHead and SteelHead Interceptor in-path IP addresses on different subnets. For more details, see the SteelHead Interceptor Deployment Guide. Multiple SteelHead Link Support A SteelHead can have multiple in-path interfaces configured so that SteelHead Interceptor can use multiple IP addresses to reach the same SteelHead. The SteelHead Interceptor only redirects traffic to one interface on the SteelHead at any time. For more details, see the SteelHead Interceptor Deployment Guide. Multiple SteelHead Support Using the steelhead communication commands, the clustered SteelHeads configure each clustered SteelHead Interceptor as a connection forwarding neighbor. Each clustered SteelHead typically has one SteelHead Interceptor in-path interface (for example, inpath0_0, but this varies by model) configured as the clustered SteelHead main interface, and the other SteelHead Interceptor interfaces configured as additional choices. Do not configure a connection between the clustered SteelHeads. You can use the RiOS data store synchronization between any local pair of SteelHeads, including SteelHead pairs in a SteelHead Interceptor cluster. You typically perform data synchronization when the load-balance configuration on the SteelHead Interceptor appliance causes similar traffic to be sent to the pair of SteelHeads. For more details, see the SteelHead Interceptor Deployment Guide. 20 SteelHead Interceptor Appliance Installation Guide
Checking Your Inventory Installing the SteelHead Interceptor Checking Your Inventory Your shipping carton contains the following items: The SteelHead Interceptor One CAT-5E straight-through cable One RS-232 serial extension cable One power cable 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 SteelHead Interceptor is shipped completely assembled, with all the equipment parts in place and securely fastened. Site Requirements Before you install the SteelHead Interceptor, make sure that your site meets the following requirements: A standard electronic environment where the ambient temperature does not exceed 95ºF (35ºC) and the relative humidity does not exceed 95% (noncondensing). An Ethernet connection available within the standard Ethernet limit. Space on a two-post or four-post, 19-inch, Telco-type mounting rack. The SteelHead Interceptor requires 3U of rack space. For details on installing the SteelHead Interceptor to a rack, see the Rack Installation Guide or the printed instructions that were shipped with the SteelHead Interceptor. A clean power source dedicated to computer devices and other electronic devices. The SteelHead Interceptor is completely assembled, with all the equipment parts in place and securely fastened. The SteelHead Interceptor is ready for installation with no further assembly required. You need a Phillips screwdriver to secure the SteelHead Interceptor to the rack. SteelHead Interceptor Appliance Installation Guide 21
Installing the SteelHead Interceptor Preparing for Registration with the SteelCentral Controller for SteelHead Preparing for Registration with the SteelCentral Controller for SteelHead If you have SteelCentral Controller for SteelHead (SCC) installed in your network to centrally manage and monitor SteelHeads, you can use a subset of SCC features to centrally manage and monitor SteelHead Interceptors. From the SCC, you can define SteelHead Interceptor groups and policies that you use to perform administrative tasks on managed SteelHead Interceptors. Use the SCC to perform the following administrative tasks on managed SteelHead Interceptors: Configuration of event notification Collection of logs Configuration of backup and restore functions SCC features not supported on the SteelHead Interceptor include the following: Automatic configuration of new SteelHead Interceptors Sending of configuration settings to SteelHead Interceptors in remote offices Initiating centralized configuration and reporting on SteelHead Interceptors For information about SCC features, see the SteelCentral Controller for SteelHead User s Guide. Registering the SteelHead Interceptor with the SCC Before you can centrally manage and monitor a SteelHead Interceptor from an SCC, the appliance must be registered with the SCC. Registration of an appliance provides the SCC with the information necessary to establish a management connection to the appliance. You can register new appliances with the SCC before you deploy them. You can also allow new appliances to automatically register with the SCC running on the default-named host. Manual Registration on the SCC Before you can deploy the SteelHead Interceptor you have to register the new SteelHead Interceptor with the SCC. Use the Appliances page of the SCC to manually register the appliance. You specify the serial number, IP address, and administrative user name and password for the SteelHead Interceptor. After you deploy the appliance, the SCC uses the appliance registration information to establish a management connection to the appliance. Automatic Registration on the SteelHead Interceptor In a new SteelHead Interceptor, default settings in the configuration specify that the appliance is to automatically register itself with the SCC reachable by the hostname riverbedcmc. The SteelHead Interceptor initiates a short-lived connection to add its IP address to an appliance registration entry on the SCC. Note: The SteelHead Interceptor default configuration setting that specifies the SCC hostname cannot be modified through the Configuration Wizard nor through the Management Console. 22 SteelHead Interceptor Appliance Installation Guide
Completing the Configuration Checklist Installing the SteelHead Interceptor Automatic Registration of New Appliances on Deployment If your network runs the SCC software on a host that is reachable by the name riverbedcmc, new SteelHead Interceptors automatically register with the SCC as soon as you connect the appliances to your network. If your network runs the SCC software on a host that is reachable by the specified hostname, new SteelHead Interceptors automatically register with the SCC as soon as you connect the appliances to your network provided that both the specified hostname and the default hostname riverbedcmc are resolvable to the same SCC IP address. Automatic Registration of New Appliances After You Modify Their Configurations If your network runs the SCC software on a host that is reachable by the specified hostname but you are unable to make the default hostname riverbedcmc resolvable to the SCC IP address, the SteelHead Interceptors will not automatically register as soon as you connect the appliances to your network. However, you can modify newly deployed SteelHead Interceptors so that they automatically register with the SCC software on a host that is reachable by the specified hostname. The following steps summarize the sequence of events for each new SteelHead Interceptor. To automatically register a new appliance after you modify the configurations 1. Connect the new SteelHead Interceptor to your network. 2. At the serial console connection to the SteelHead Interceptor, complete the configuration wizard process. For details, see Completing the Configuration Checklist on page 23. 3. At the serial console connection, enter CLI commands to modify the appliance configuration, replacing the default SCC hostname riverbedcmc with the name <hostname>. For details, see Completing the Configuration Checklist on page 23. Completing the Configuration Checklist Before you begin, consult the Rack Installation Guide for detailed information about how to install your model to a rack. The following checklist displays the parameters you specify to complete the initial configuration of the SteelHead. Be prepared to provide values for these parameters. Appliance Parameter Your Value SteelHead Interceptor Hostname IP address Netmask Default gateway Domain Name System (DNS) IP address Domain Name SteelHead Interceptor Appliance Installation Guide 23
Installing the SteelHead Interceptor Powering On the System Appliance Parameter Your Value SCC with which the SteelHead Interceptor is to automatically register. Default hostname is riverbedcmc. (If applicable) Hostname (For DNS) IP address (For DNS) Alias, if used Powering On the System This section describes how to connect and power on the SteelHead Interceptor. To power on the system 1. If your model has a master power switch, make sure it is in the off position (on the rear panel). 2. Plug the alternating current (AC) power cord provided in your shipment into the SteelHead Interceptor. 3. Plug the AC power cord into an uninterrupted AC outlet. 4. If your model has a master power switch, press the master power switch (ON). 5. Press the system power switch on the front of the SteelHead Interceptor. 6. Check the status lights on the SteelHead Interceptor. For details, see Status Lights and Ports on page 37. Running the Configuration Wizard To access the configuration wizard and the Interceptor CLI, you establish a serial connection using a terminal emulator program. To run the configuration wizard 1. Plug the serial cable provided in your shipment into the console port on the SteelHead Interceptor. Depending on your appliance, the Console port is either a DB9F port or an RJ45 port. (For port details for your appliance model, see Appendix A, Technical Specifications. ) The appropriate serial cable ships with your appliance. Figure 2-1. Connecting the SteelHead Interceptor Appliance 24 SteelHead Interceptor Appliance Installation Guide
Running the Configuration Wizard Installing the SteelHead Interceptor 2. Start your terminal emulation program, such as Tera Term Pro or HyperTerminal. The terminal device must have the following settings: Baud rate: 9600 bps Data bits: 8 Parity: none Stop bits: 1 No flow control 3. Log in as an administrator. 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 SteelHead Interceptor using the configuration wizard. 4. To start the configuration wizard, enter yes at the system prompt. Configuration wizard. Do you want to use the wizard for initial configuration? yes Press Enter to enter the default value; press? for help; press Ctrl+B to go back to the previous step. 5. Complete the configuration wizard steps as described in the following table. Wizard Prompt Description Example Step 1: Hostname? Step 2: Use DHCP? Step 3: Primary IP address? Step 4: Netmask? Step 5: Default gateway? 10.0.0.1 Step 6: Primary DNS server? Enter the hostname for the SteelHead Interceptor. You are given the option to enable DHCP to automatically assign an IP address to the primary interface for the SteelHead Interceptor. Riverbed recommends that you do not set DHCP. The default value is no. Enter the IP address for the SteelHead Interceptor. Enter the netmask for the network on which the SteelHead Interceptor is to reside. Enter the default gateway for the network on which the SteelHead Interceptor is to reside. Enter the primary DNS server for the network on which the SteelHead Interceptor is to reside. Step 1: Hostname? minna Step 2: Use DHCP? no Step 3: Primary IP address? 10.0.0.74 Step 4: Netmask? 255.255.0.0 Step 5: Default gateway? 10.0.0.1 Step 6: Primary DNS server? 10.0.0.2 SteelHead Interceptor Appliance Installation Guide 25
Installing the SteelHead Interceptor Running the Configuration Wizard Wizard Prompt Description Example Step 7: Domain name? Enter the domain name for the network on which the SteelHead Interceptor is to reside. If you set a domain name, you do not need to specify the domain names when you set up remote SteelHeads to be load-balanced by the SteelHead Interceptor. Step 7: Domain name? example.com Note: When you configure DNS server settings, map interceptor to the IP address for the SteelHead Interceptor. Step 8: Admin password? Riverbed strongly recommends that you change the default password at this time. The password must be minimum of six characters. The default administrator password is password. Step 8: Admin password? xxxyyy The system confirms your settings. You have entered the following information: 1. Hostname: minna 2. Use DHCP: no 3. Primary IP address: 10.0.0.74 4. Netmask: 255.255.0.0 5. Default gateway: 10.0.0.1 6. Primary DNS server: 10.0.0.2 7. Domain name: example.com 8. Admin password: (unchanged) To change an answer, enter the step number to return to. Otherwise hit <enter> to save changes and exit. Choice: The SteelHead Interceptor configuration wizard automatically saves your initial configuration settings. 6. To log out of the system, enter the exit command at the system prompt: > exit 7. (Optional) To configure the SteelHead Interceptor to automatically register with a SCC other than riverbedcmc, enter the following commands at the user mode system prompt of the administrative CLI: enable configure terminal show cmc cmc hostname <hostname> cmc enable show cmc write memory exit exit The following example shows how to enter CLI commands at the SteelHead Interceptor amnesiac to change the auto-registration SCC hostname from riverbedcmc to rvbd_cmc_host9: amnesiac > enable amnesiac # configure terminal 26 SteelHead Interceptor Appliance Installation Guide
Configuring In-Path SteelHeads Installing the SteelHead Interceptor amnesiac (config) # show cmc CMC auto-registration enabled: CMC auto-registration hostname: Managed by CMC: CMC hostname: Auto configuration status: Last message sent to cmc: yes riverbedcmc no Inactive n/a amnesiac (config) # cmc hostname rvbd_cmc_host9 amnesiac (config) # cmc enable amnesiac (config) # show cmc CMC auto-registration enabled: CMC auto-registration hostname: Managed by CMC: CMC hostname: Auto configuration status: Last message sent to cmc: yes rvbd_cmc_host9 no Inactive n/a amnesiac (config) # write memory amnesiac (config) # exit amnesiac # exit amnesiac > _ For detailed information about the CLI commands, see the Riverbed Command-Line Interface Reference Manual. Configuring In-Path SteelHeads The SteelHead Interceptor manages connections to LAN-side SteelHeads. Connecting In-Path SteelHeads to Your Network You can connect an in-path SteelHead to your network. To connect an in-path SteelHead to your network 1. Plug one end of the straight-through cable into the LAN in-path interface of the SteelHead Interceptor (lan0_0, for example). Plug the other end of the cable to the LAN switch (this can be any port on your LAN switch that acts as a host). 2. Plug one end of the cross-over cable into the WAN in-path interface of the SteelHead Interceptor (wan0_0, for example). Plug the other end of the cable to the WAN router. SteelHead Interceptor Appliance Installation Guide 27
Installing the SteelHead Interceptor Configuring In-Path SteelHeads Figure 2-2 shows the basic cable connections between network devices. Figure 2-2. Basic Deployment: Cable Connections Between Network Device Figure 2-3 shows the basic cable connections between network devices when you deploy an SteelHead Interceptor with bypass cards. Figure 2-3. Basic Deployment: Cable Connections Between Network Device When You Use Bypass Cards For specifications on supported bypass cards, see the Network Interface Card Installation Guide. 28 SteelHead Interceptor Appliance Installation Guide
Configuring In-Path SteelHeads Installing the SteelHead Interceptor Figure 2-4 shows the cable connections between network devices deployed to support failover. Use a crossover cable to connect the SteelHead Interceptors to each other. Figure 2-4. Serial Deployment to Provide Failover Support Figure 2-5 shows the cable connections between network devices deployed to support networks with asymmetric routes. Figure 2-5. Parallel Deployment in Asymmetric Networks SteelHead Interceptor Appliance Installation Guide 29
Installing the SteelHead Interceptor Configuring In-Path SteelHeads Figure 2-6 shows a serial and parallel deployment designed to provide failover and handle asymmetric routes. Figure 2-6. Parallel Deployment in Asymmetric Networks 30 SteelHead Interceptor Appliance Installation Guide
Verifying Your Connections Installing the SteelHead Interceptor Verifying Your Connections This section describes how to verify that you have properly connected the SteelHead Interceptor. To verify your connections 1. Check the status lights to verify that the SteelHead Interceptor is connected properly. 2. From a remote LAN-side SteelHead, connect to the CLI. ssh admin@host.domain or ssh admin@ipaddress 3. Enter the following ping commands to verify the connections: ping -I <primary-ip-address> <primary-default-gateway> ping -I <inpath-ip-address> <address-on-lan-side> ping -I <inpath-ip-address> <address-on-wan-side> Next Steps After you have installed and initially configured the SteelHead Interceptor, refer to the SteelHead Interceptor User s Guide to complete the next steps. Step 1. Open the Interceptor Management Console and become familiar with its navigation and administrative features. Reference Chapter 1 2. Configure in-path rules to pass through or deny traffic you do not want to optimize. Chapter 2 3. Add to the configuration the cluster of neighbor SteelHeads you want to load balance. Chapter 2 4. Configure peering with other SteelHead Interceptors, if applicable. Chapter 2 5. Configure load-balancing rules. Chapter 2 6. Verify connections among your network devices by viewing Interceptor Management Console reports. Chapter 3 7. Review and, if you choose, modify the SteelHead Interceptor default host and networking settings. Chapter 4 SteelHead Interceptor Appliance Installation Guide 31
Installing the SteelHead Interceptor Next Steps 32 SteelHead Interceptor Appliance Installation Guide
APPENDIX A Technical Specifications This chapter summarizes the SteelHead Interceptor technical specifications, status lights, and status beeps. This chapter includes the following sections: SteelHead Interceptor 9600 Specifications on page 33 SteelHead Interceptor 9350 Specifications on page 37 SteelHead Interceptor 9600 Specifications This section describes the status lights, ports, and technical and environmental specifications. SteelHead Interceptor Appliance Installation Guide 33
Technical Specifications SteelHead Interceptor 9600 Specifications Status Lights and Ports Figure A-1 and Figure A-2 show the status light and port locations. Figure A-1. SteelHead Interceptor 9600 Front Panel with LEDs and Buttons Figure A-2. SteelHead Interceptor 9600 Back Panel Note: By default, the SteelHead Interceptor 9600 ships with a bypass card in slot 1. The default interface names are LAN1_0, WAN1_0, LAN1_1, and WAN1_1. This appliance does not have an inpath0_0 interface as found on earlier appliances and by default the SteelHead Interceptor 9600 uses inpath1_0 and inpath1_1. 34 SteelHead Interceptor Appliance Installation Guide
SteelHead Interceptor 9600 Specifications Technical Specifications The following table summarizes the appliance LEDs and buttons. Reference LED/Button Description 1 2 3 10 System ID Button with Integrated LED NMI Button Network Activity LED Primary Auxiliary Maintenance = Blue 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 Intelligent Platform Management Interface (IPMI) ipmitool 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. Pressing the NMI button puts the appliance in a halt state and issues a nonmaskable interrupt (NMI). This 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. Link = Green Activity = Blinks green. The blink rate is consistent with the amount of network activity. The appliance does not use the LEDs 4 and 9 shown in Figure A-1. 5 System Cold Reset Button Pressing this button reboots the appliance. 6 System Status LED The System Status LED shows the current health of the server system. 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 LEDs on Disk Drives LEDs on Primary and AUX Ports Activity LED Read/Write Activity = Blinks green Disk Fault LED Failed Disk = Orange RAID Rebuild = Blinks orange Left LED Link = Green Activity = Blinks green Right LED 10 MB/sec data rate = No light (with link on left LED) 100 MB/sec data rate = Green 1000 MB/sec data rate = Yellow SteelHead Interceptor Appliance Installation Guide 35
Technical Specifications SteelHead Interceptor 9600 Specifications Reference LED/Button Description LEDs on Default 4 Port Copper Bypass Card Link/Activity LED Link = Green Activity = Blinks green Speed/Bypass/Disconnect LED 1000Mbit/s = Yellow 100Mbit/s = Green 10Mbit/s = Off Bypass = Blinks green Disconnect = Blinks yellow LEDs on Power Supply 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 Technical Specifications The following table summarizes the technical specifications for the systems. SteelHead Interceptor 9600 Form Factor Hard Disk Dimensions (LxWxH) Weight (without packaging) Voltage Frequency PSU 2U 2 x 1000 GB HDD 27.87 x 17.24 x 3.45 in. 707.8 x 438 x 87.6 mm 42 lbs (19.05 kg) 100 127 V, 200 240 V 2 x 770 W 100 127 VAC/8.2 A, 50/60 Hz 200 240 VAC/4.4 A, 50/60 Hz PCI Slots 6 Included Bypass Ports/ Max # Ports 4/20 36 SteelHead Interceptor Appliance Installation Guide
SteelHead Interceptor 9350 Specifications Technical Specifications 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 Interceptor 9600 Interceptor 9600 Configuration All (L/M/H) All (L/M/H) PSU Type 2 x 770 W 2 x 770 W AC Input 120 V 230 V Max. Amps. 2.86 1.45 Max. Watts 284 276 Typical Watts 221 221 Max VA 278 278 Power Factor 99.16 99.16 BTU (Typical) 774 753 Environmental Specifications The following table summarizes the environmental requirements for the systems. SteelHead Interceptor 9600 Operating Acoustic Temperature (Operating) Temperature (Storage) Relative Humidity 7.0 BA Sound Pressure (Typical) 10º 35ºC 50 95ºF -40º 70ºC -40º 158ºF 50% to 90%, noncondensing with a maximum wet bulb of 28ºC (at temperatures from 25 to 35ºC) SteelHead Interceptor 9350 Specifications This section describes the status lights, ports, and technical specifications for the 9350 appliance. Status Lights and Ports This section shows the status lights and interface names for the SteelHead Interceptor 9350 appliance. SteelHead Interceptor Appliance Installation Guide 37
Technical Specifications SteelHead Interceptor 9350 Specifications Figure A-3, Figure A-4 and Figure A-5 show the status lights and interface names for the SteelHead Interceptor 9350 appliance. Figure A-3. Front Panel SteelHead Interceptor 9350 Appliance Figure A-4. Disk Drive Numbers SteelHead Interceptor 9350 38 SteelHead Interceptor Appliance Installation Guide
SteelHead Interceptor 9350 Specifications Technical Specifications Figure A-5. Back Panel SteelHead Interceptor 9350 Appliance The following table describes the four onboard bypass port LEDs for the SteelHead Interceptor 9350. LED Bypass/Block (Disconnect) Right LED Left LED Condition Solid orange in bypass or block (disconnect) mode GB = Orange 100 MB = Green 10 MB = No light Solid green on link, blinks green for activity SteelHead Interceptor Status Beeps In the event of fan failure or power supply failure, the Interceptor emits three beep sounds. Technical Specifications The following table summarizes the technical specifications for the SteelHead Interceptor. Specification SteelHead Interceptor 9350 Form Factor Dimensions (height x width x depth) Gross Weight AC Voltage Power Redundancy Power-Watts 3U 5.2 x 17 x 25.72 in. 131.9 x 431.6 x 653.4 mm 51 lbs (23.2 kg) 100 240 V, 50 60 Hz, 4.9 A Double 320 W Power-Amps @ 110 V (load) (watts/110 V) 3.2 SteelHead Interceptor Appliance Installation Guide 39