Cascade Installation Guide Version 9.0 February 2011

Transcription

1 Version 9.0 February 2011

2 Riverbed Technology, Incorporated. All rights reserved. Riverbed Technology, Riverbed, Steelhead, RiOS, Interceptor, Riverbed Cascade, Cascade and the Riverbed logo are trademarks or registered trademarks of Riverbed Technology, Inc. All other trademarks used or mentioned herein belong to their respective owners. Portions of Cascade products contain copyrighted information of third parties. Title thereto is retained, and all rights therein are reserved, by the respective copyright owner. PostgreSQL is (1) Copyright The PostgreSQL Development Group, and (2) Copyright the Regents of the University of California; PHP is Copyright The PHP Group; gnuplot is Copyright , 1998, 2004 Thomas Williams, Colin Kelley; ChartDirector is Copyright 2007 Advanced Software Engineering; Net-SNMP is (1) Copyright 1989, 1991, 1992 Carnegie Mellon University, Derivative Work 1996, Copyright 1996, The Regents of The University of California, (2) Copyright Network Associates Technology, Inc., (3) Copyright Cambridge Broadband Ltd., (4) Copyright 2003 Sun Microsystems, Inc., (5) Copyright Sparta, Inc. and (6) Copyright 2004 Cisco, Inc. and Information Network Center of Beijing University of Posts and Telecommunications, (7) Copyright Fabasoft R&D Software; Apache is Copyright by The Apache Software Foundation; ILOG JView Component Suite is Copyright ILOG, Inc.; Click is (1) Copyright Massachusetts Institute of Technology, (2) Copyright Riverbed Technology, Inc., (3) Copyright International Computer Science Institute, and (4) Copyright Regents of the University of California; OpenSSL is (1) Copyright The OpenSSL Project and (2) Copyright Eric Young Netdisco is (1) Copyright 2003, 2004 Max Baker and (2) Copyright 2002, 2003 The Regents of The University of California; SNMP::Info is (1) Copyright Max Baker and (2) Copyright 2002, 2003 The Regents of The University of California; mm is (1) Copyright Ralf S. Engelschall and (2) Copyright The OSSP Project; ares is Copyright 1998 Massachusetts Institute of Technology; libpq++ is (1) Copyright The PostgreSQL Global Development Group, and (2) Copyright 1994 the Regents of the University of California; Yahoo is Copyright 2006 Yahoo! Inc.; pd4ml is Copyright zefer.org; Rapid7 is Copyright Rapid7 LLC; CmdTool2 is Copyright 2008 Intel Corporation; QLogic is Copyright QLogic Corporation; Tarari is Copyright 2008 LSI Corporation; Crypt_CHAP is Copyright , Michael Bretterklieber; Auth_SASL is Copyright Richard Heyes; Net_SMTP is Copyright The PHP Group; XML_RPC is (1) Copyright Edd Dumbill, (2) Copyright The PHP Group; Crypt_HMAC is Copyright The PHP Group; Net_Socket is Copyright The PHP Group; PEAR::Mail is Copyright The PHP Group; libradius is Copyright 1998 Juniper Networks. Other product names, brand names, marks, and symbols are registered trademarks or trademarks of their respective owners. In respect of so-called open source or community source Third Party Materials only: PostgreSQL and its use are subject to the BSD License; Netdisco and its use are subject to the BSD License; SNMP::Info and its use are subject to the BSD License; PHP and its use are subject to the PHP License; gnuplot and its use are subject to the gnuplot License; Net-SNMP and its use are subject to the CMU/UCD and the BSD Licenses; Apache and its use are subject to The Apache Software License, Version 2.0; Click and its use are subject to the Click License; OpenSSL and its use are subject to the OpenSSL license and SSLeay license; libmcrypt and its use are subject to the Gnu Lesser General Public License; mhash and its use are subject to the Gnu General Public License; mm and its use are subject to the Ralf S. Engelschall license; ares and its use are subject to the ares license; libradius and its use are subject to the BSD License; libpq++ and its use are subject to the BSD License; Nessus and its use are subject to the Gnu General Public License; Yahoo and its use are subject to the BSD license; e1000 and its use are subject to the Gnu General Public License; ixgb and its use are subject to the Gnu General Public License; Net-SNMP and its use are subject to the CMU/UCD and BSD licenses; Crypt_CHAP and its use are subject to the BSD ii

3 License; Auth_SASL and its use are subject to the BSD License; Net_SMTP and its use are subject to the PHP License; XML_RPC and its use are subject to the PHP License; Crypt_HMAC and its use are subject to the PHP License; Net_Socket and its use are subject to the PHP License; PEAR::Mail and its use are subject to the PHP and BSD Licenses; xajax and its use are subject to the Gnu General Public License; parted and its use are subject to the Gnu General Public License; busybox and its use are subject to the Gnu General Public License; DBAN and its use are subject to the Gnu General Public License; Linux and its use are subject to various licenses. Individual license agreements can be viewed at the following location: This software is based in part on the work of the Independent JPEG Group. This software is based in part on the work of the FreeType team. This manual is for informational purposes only. Addresses shown in screen captures were generated randomly by simulation software and used only on an internal network. They are for illustrative purposes only and are not intended to represent any real traffic involving any registered IP or MAC addresses. The content of this manual is furnished on a RESTRICTED basis and is subject to change without notice and should not be construed as a commitment by Riverbed Technology, Incorporated. Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in Subparagraphs (c) (1) and (2) of the Commercial Computer Software Restricted Rights at 48 CFR , as applicable. Riverbed Technology, Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. iii

4 iv

5 Contents 1. Inventory and inspection Preparations for installation... 1 Data sources... 1 Rack space... 2 Power... 3 Cooling... 3 Network connections... 3 Management port... 3 Intermodule communication (Enterprise Profiler only)... 3 Monitored network (Express and Sensor only)... 4 NAS port (Profiler and Express only)... 4 RMM port... 5 Access to network... 5 Communication between Cascade appliances... 5 Access to other network services... 6 Access to traffic flow data (Express and Gateway)... 6 Access to forwarding destinations (Gateway only) Mounting and powering... 7 Safety information... 7 Hardware installation Standard Profiler installation... 8 Configuration information... 8 Configuring the Standard Profiler Network connections Additional configuration Verification Verifying Profiler operation Verifying Remote Management Module access Exiting the installation process v

6 5. Enterprise Profiler installation Configuration information Configuring the Enterprise Profiler Configuring the Management Module Configuring Remote Management Modules Additional configuration Verification Verifying Profiler operation Verifying Remote Management Module access Exiting the installation process Express installation Configuration information Configuring the Express Network connections Additional configuration Verification Verifying Express operation Verifying Remote Management Module access Exiting the installation process Sensor installation Configuration information Configuring the Sensor Network connections Additional configuration Verification Verifying Sensor operation Verifying Remote Management Module access Exiting the installation process Sensor-VE installation Prerequisites Configuration information Verify RSP installation Download the Sensor-VE package to the Steelhead (upgrades only) vi

7 Install Sensor-VE in an RSP Package Slot Configure and enable the slot Configure the Sensor-VE monitor interfaces Configure the Sensor-VE management interface Complete the Sensor-VE setup Network connections Verify Sensor-VE operation Exiting the installation process Gateway installation Configuration information Configuring the Gateway Network connections Additional configuration Identifying Profilers Flow forwarding Verification Verifying Gateway operation Verifying Remote Management Module access Exiting the installation process SAN installation Introduction Unpacking and inspection Preparing to install the hardware Card mounting considerations Cabling considerations Installing the FC HBA card Preparing to configure the software Contacting Riverbed Support vii

8 viii

9 About this guide This guide describes installing the Riverbed Cascade family of network appliances. The Cascade Sensor-VE is installed on the Riverbed Services Platform on a Riverbed Steelhead. All other Cascade appliances are installed in a standard rack. This guide describes connecting them to your network, verifying network connectivity, and verifying that they are receiving and processing traffic data. When these tasks are completed, the Cascade appliance is ready to configure operationally. Operational configuration is described in the online help system. At least one data source must be provided to the Cascade appliance in order to verify the installation. Therefore, the most streamlined approach is to configure your data sources to send traffic data to the Cascade appliance as part of preparing to begin the installation. The Preparations for Installation section of this guide discusses topics that should be considered before mounting and cabling the Cascade appliance. Sections 1 through 3 apply to all Cascade chassis. For Cascade Sensor-VE, go directly to Section 8. Sections 4 through 8 each cover one product. Section 9 covers the hardware installation of the optional SAN interface. Safety Notice To reduce the risk of personal injury or equipment damage, observe the safety warnings and cautions that are provided in the Riverbed Safety and Compliance Guide. ix

10 x

11 1. Inventory and inspection Cascade Installation Guide 1. Check the shipping documentation to ensure that all cartons have arrived. 2. If you have not already done so, visually inspect each carton for indications of damage. 3. If any cartons are damaged or missing, contact Riverbed Support before continuing. Phone United States and Canada: Phone outside U.S. and Canada: support@riverbed.com Web: 4. Unpack the contents of the shipping cartons and inventory the contents against the shipping documentation. 5. If any components of the order are damaged or missing, contact Riverbed Support. 2. Preparations for installation Data sources Before installing the chassis, ensure that the following considerations have been addressed: Data sources Rack space Power Cooling Network connections Access to network The Cascade appliance must be receiving traffic information from at least one source in order for you to verify successful installation and configuration. There are two approaches to setting up data sources: Set up the available data sources and point them to the IP address of the Cascade appliance before you install it. Install the Cascade appliance up to the point of verification, go install or configure the data sources, and then return to the Cascade appliance to complete the installation verification. 1

12 Rack space It is preferable to configure all the data sources that are available at the time you install the Cascade appliance. However, Cascade operation can be confirmed with just one data source. The data sources required by Cascade appliances are as follows: Profiler The Standard Profiler and Enterprise Profiler obtain traffic information from Riverbed Cascade Sensors and Riverbed Cascade Gateways. Express The Riverbed Cascade Express obtains traffic information from taps or mirror ports on the monitored network, or from NetFlow, IPFIX, Packeteer FDR or sflow sources. Sensor The Riverbed Cascade Sensor obtains traffic information from taps or mirror ports on the monitored network. How many points on the network can be monitored depends on which Sensor model you have. Sensor-VE The Riverbed Cascade Sensor-VE is a virtual edition of the Sensor. Instead of running on Cascade hardware, it runs as a virtual machine on a Riverbed Steelhead appliance. It monitors the LAN interfaces of the Steelhead appliance via the Riverbed Services Platform (RSP). The Sensor-VE can also monitor traffic from taps or mirror ports on the monitored network using the Steelhead Aux port. Gateway The Riverbed Cascade Gateway obtains traffic information from NetFlow, IPFIX, Packeteer FDR or sflow sources. Ensure that the Cascade appliance you are installing has the required data sources available. If the Cascade appliance is to receive flow data from NetFlow-enabled devices, enable the SNMP ifindex persistence feature of the NetFlow source to ensure consistency of interface reporting by the Profiler or Express that is to receive the flow data. Refer to the Prerequisites paragraph in Section 8 Sensor- VE installation for an example of enabling the Riverbed Steelhead SNMP ifindex persistence feature. Each Cascade appliance chassis requires a 2U rack space and is best mounted in a 4-post, 19-inch rack or cabinet. It can also be mounted in a 2-post, 19-inch rack, but this requires a deep shelf. Height: 8.7 cm, 3.44 in. (2U) Width: 45.1 cm, 17.8 in. Depth: 70.5 cm, 27.8 in. Weight: 29.5 kg, 65 lbs. 2

13 The Enterprise Profiler requires a 2U rack space for each of its modules. It includes a minimum of three chassis: Management Module Database Module Expansion Module (one or more) Power Cooling Each chassis has a 750-watt power supply that requires: 100V-127V, 50/60 Hz, 11A, or 200V-240V, 50/60 Hz, 5.5A Required cooling is approximately 3300 BTU/hour for each chassis, depending on the model. Ambient air should be: Air temperature: 10 to 35 C (50 to 95 F) Humidity: 8% to 80% Network connections Management port Each Cascade appliance chassis is equipped with a 100/1000baseTX management port that must connect to a hub or switch on the management network. The chassis management port is set by default for auto-negotiation. Ensure that a straight-through cable to a hub or switch port on the management network is available at the rack location. Ensure that the management network switch port is set to establish a connection at 100 or 1000 Mb/s and full duplex. Intermodule communication (Enterprise Profiler only) Modules in the Enterprise Profiler communicate with one another by means of a customer-supplied switch. Profiler modules are equipped with 1000baseTX ports that are set by default for auto-negotiation. Ensure that: The management network has a switch port for each Enterprise Profiler module. These switch ports are configured to establish a connection using 1000 Mb/s and full duplex. 3

14 No devices on the management network are already using the default addresses of the Profiler modules: o Management Module o Database Module o Expansion Module Straight-through cables are available at the rack locations for connecting the Profiler modules to the switch. (One cable per chassis.) A terminal device (laptop, KVM, etc.) is available on the management network for logging in to the Profiler user interface. Monitored network (Express and Sensor only) All Cascade Sensor and Express appliances (except flow-monitoring-only Express models) connect via straight-through cables to taps or mirror ports on the monitored network. Models that use electrical cables include 2-port 10/100/1000baseTX (RJ45) connectors. Models that use optical cables include 2-port 1000baseSX connectors. Ensure that optical cables are multimode fiber with LC connectors. Sensor configurations include: 1-port copper; 10/100/1000 Mbps; RJ45 connector 2-port copper, 10/100/1000 Mbps; RJ45 connectors 2-port fiber, 1 Gbps; multimode fiber with LC connectors 2-port fiber, 1 Gbps; single mode fiber with LC connectors 2-port fiber, 10 Gbps; single mode fiber with LC connectors 2-port fiber; 10 Gbps; multimode fiber with LC connectors 4-port copper, 10/100/1000 Mbps; RJ45 connectors 4-port fiber; 1 Gbps; multimode fiber with LC connectors Ensure that the necessary mirror ports are set up and that the cables are available in the rack where the Sensor or Express is to be installed. NAS port (Profiler and Express only) If the Cascade appliance uses a NAS device, it can be connected via a crossover cable directly to the AUX port. Alternatively, the Cascade appliance can access a NAS device over the management network. If the Cascade appliance will use a NAS device on the management network, then: It must have auto-negotiation on. The switch port that it connects to must have auto-negotiation on and must have 1000Mb/s capabilities configured. 4

15 Access to network Cascade Installation Guide If the NAS device will be connected directly to the Cascade appliance, then the Cascade appliance and the NAS device must have the same settings for speed, duplex or auto-negotiation modes on the NAS link. The link between the Profiler and the NAS device must have 1000Mb/s capabilities for correct performance. Refer to the vendor s documentation or contact Riverbed Support for assistance for configuration details. RMM port Each Cascade appliance chassis includes a remote chassis management module. The Intel Remote Management Module (Intel RMM) is operating whenever power is available to the chassis. It allows you to power the appliance on and off remotely, over the network. It can also be used for remote troubleshooting in the event of a hardware problem. The RMM operates independently of other functions and provides dedicated access to the hardware level of the Cascade appliance. It has its own network address and provides its own web-based user interface, which you can access with a web browser. The network address for the RMM does not need to be on the same subnet as the address for the Cascade appliance management interface. The RMM has a 100baseTX port that must connect to a hub or switch on the management network. The RMM port is set by default for auto-negotiation. Ensure that a straight-through cable to a hub or switch port on the management network is available at the rack location. Ensure that the management network switch port is set to establish a connection at 100 Mb/s and full duplex. Communication between Cascade appliances If you lock down your network on a port-by-port basis, ensure that the following ports are open between Cascade appliances: TCP/22 (ssh) This is needed for the Profiler to transfer upgrade packages to other Cascade devices that are connected to it. TCP/443 (https) Secure web-based management interfaces. TCP/8443 Exchange of encryption certificates between Cascade appliances. TCP/41017 Encrypted communication between Profiler and Sensors or Gateways. UDP/123 (ntp) Synchronization of time between a Sensor or Gateway and Profiler. 5

16 Access to other network services TCP/22 (ssh) This is needed for secure shell access to Cascade software components and for the appliance to obtain information from servers via scripts. UDP/161 (snmp) The Profiler and Express use SNMP to obtain interface information from switches. Also, management systems use this port to read the Cascade appliance MIB. TCP/5432 (odbc) If you will be allowing other applications to access the Profiler or Express internal database via ODBC, then you must allow traffic on this port If you will be using the Profiler or Express user identification feature with a Microsoft Active Directory domain controller, then you must allow traffic on port Vulnerability scanner ports If you will be using the Profiler or Express vulnerability scan feature, then you must allow traffic on the port that the Cascade appliance is to use for accessing the vulnerability scanner server. Obtain vulnerability scanner server addresses and port numbers from the administrator of those systems. The default ports are as follows: o Nessus: 1241 o ncircle: 443 o Rapid7: 3780 o Qualys: Requires external https access to qualysapi.qualys.com (Note: This is separate from qualysguard.qualys.com.) o Foundstone: 3800 Access to traffic flow data (Express and Gateway) The ports used by the NetFlow, IPFIX, Packeteer FDR, and sflow data sources must be open between the source devices and the Express or Gateway. Access to forwarding destinations (Gateway only) The Gateway can forward NetFlow, IPFIX, Packeteer FDR, and sflow data to other destinations. It sends data to the ports that you specify during configuration. These ports must not be blocked. 6

17 3. Mounting and powering Safety information Follow the safety precautions outlined in the Riverbed Safety and Compliance Guide when installing and setting up your system. The guide contains the safety information in multiple languages. Before you install, operate, or service your system, you must be familiar with the safety information. Note: Failure to follow these safety guidelines can result in injury or damage to the equipment. Mishandling of the equipment voids all warranties. Please read and follow safety guidelines and installation instructions carefully. Hardware installation CAUTION: When you are ready to mount the chassis in the rack, 1. Locate the rails in the shipping carton. 2. Locate the rail installation instructions in the accessory box. 3. Mount the rails in the rack, as described in the instructions. 4. Place the chassis into the component mounting channels of the rails and ensure that the component release levers lock the chassis securely in the rails, as described and illustrated in the instructions. Observe the safety cautions in the mounting instructions. 5. Pressing the slide extension release levers, slide the chassis into the rack. 6. Connect the power cable to the chassis and to rack power. The system starts up automatically when power is connected. However, you can use the power button to power off the system if necessary. The bezel can be locked in place. The key is provided in the accessory box. 7

18 The bezel covers the power button and prevents people from accidentally switching off the Cascade appliance. The Power button is located near the center of the control panel on the upper-right side of the front of the chassis. 4. Standard Profiler installation This section describes the hardware and software configuration necessary to install a Standard Profiler. Refer to Section 3 mounting instructions. Configuration information Profiler host name:* Profiler IP address:* Netmask:* Default gateway:* When you configure the Profiler, you will be asked to provide configuration information. Information that is required to complete the installation is listed in the table that follows with an asterisk (*). Items not marked with an asterisk are optional during installation and can be specified afterwards on the Profiler Configuration General Settings page if necessary. It may be useful to write the configuration values in the blank column of the table so that you can refer to them during the configuration step or afterward. DNS name resolution for hosts (enable or disable): Primary DNS server IP address: Secondary DNS server IP address: DNS search domain: Management interface port settings: 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate Switch port settings: The settings of the switch port or hub that the Profiler management port connects to. (Auto-negotiate is recommended if there will be no NAS on the management network.) NTP server IP addresses:* Applies only if Profiler is being synchronized to an external NTP server. Enter one or more addresses as a comma-separated list. 8

19 Time Zone: Flow encryption certificate (default or new certificate): For faster installation, use the default encryption certificate shipped with the Profiler and then generate a new certificate later. SNMP information: Profiler is set by default to use SNMP Version 1 and the SNMP community name mazu (all lowercase) to allow MIB browsing. If you are configuring SNMP at this time, obtain the necessary V1 or V3 information. Outgoing mail server name, port number, and From address. Applies only if you will be specifying a server that Profiler is to use for sending reports or alert notifications. Inside addresses: IP addresses or address ranges of hosts that the Profiler is to track individually. The default values are 10/8,172.16/12, /16 Security Profile settings:* You can use either three traffic collection profiles (weekdays, weeknights, and weekends) or four (weekdays, weeknights, Saturdays, and Sundays). After installation, you can define others. You can also specify the times when weekdays begin and end (default times are 9:00 am to 5:00 pm). NAS setup (IP address*, partition name*, directory name, and partition size*): Applies only if you are using a NAS device and are not using the default Profiler settings. Password to use for your initial Profiler login:* The default password admin. New password to enter when prompted to change the initial Profiler password:* Applies only to systems not previously configured. Remote Management Module IP address Remote Management Module netmask Remote Management Module gateway 9

20 Service Management Leave this set to ByLocation unless you are requested to choose another group type for service locations. Configuring the Standard Profiler The first time you log in to a newly-installed system, it displays an initial Setup page. This is a one-time display. After you set up the initial configuration, you can make subsequent configuration changes on the Configuration pages. To configure the Profiler, you need a separate PC and a crossover cable. This PC must have an Ethernet port configured for TCP/IP networking. It must also be running Mozilla Firefox or Microsoft Internet Explorer. The LAN interface adapter settings of this PC must be set to: IP Address: Network mask: Gateway: Using these settings, connect to the Profiler as follows: 1. Use a crossover Ethernet cable to connect the Ethernet port of your PC to the Management connector on the left rear of the Profiler. 2. Point your browser to This displays the login page. 3. Log in with the default user name admin and the default password admin. This displays the Setup page. 4. Fill in all the required fields (marked with an asterisk) on the Setup page. 10

21 11 Cascade Installation Guide

22 5. In the RMM Settings section, click Set up RMM. This opens a setup page. 6. Enter the factory preset username admin and password password in the setup popup. 7. Enter the RMM network interface IP address, netmask and gateway and click OK. 8. Check to ensure that the new RMM address information is displayed in the RMM Settings section. 9. At the bottom of the Setup page, there is a checkbox labeled Power down after configuration. If the Profiler is mounted in the rack and you are ready to connect it to the network, leave the Power down after configuration box unselected and click Configure Now. If the Profiler must be powered off and mounted in the rack before it can be connected to the network, select the Power down after configuration box and click Configure Now. 10. When you click Configure Now, you will be prompted to change the password. The password you enter here must be the one you will use after this point in the procedure. Enter your new password. 11. When the password change operation is completed, exit from the browser session and disconnect the crossover cable from the Profiler. Additional configuration tasks, such as specifying a traffic collection profile scheme, which are not available on the Setup page, can be performed by logging in to the Profiler GUI after it is connected to the management network. If the Profiler is mounted in the rack and ready to connect to the network, proceed to the next section, Network connections. If the Profiler still needs to be mounted, wait for it to power down and then mount it in the rack as described in the Section 3, Mounting and powering, before proceeding to the next section. 12

23 Network connections Cascade Installation Guide After the Profiler is mounted, configured, and has been powered on for more than two minutes, connect the network cable and verify the connections as follows: 1. Connect a cable from your management network to the Management connector on the left rear of the Profiler. This is the same connector that you used to configure the Profiler. 2. Connect a cable from the network to the RMM connector on the right rear of the Profiler. The RMM connection and the Profiler management connection can be on different subnets, but these must correspond to the addresses you assigned for each interface on the Setup page. 3. Point your browser to the Profiler IP address that you specified on the Setup page during the configuration task. This displays the login page. 4. Log in to the admin account with the password you specified at the end of the configuration task. 5. Navigate to the System Devices/Interfaces page and check the status of the Sensor or other data source devices on the Devices tab. When a data source comes on line, the Profiler begins collecting data. At least one data source must be listed with a green status indicator before you can complete the Profiler installation verification step. 13

24 If no data sources are listed on the System Devices/Interfaces page Devices tab, then Profiler installation and configuration cannot be verified. Set up at least one data source device (preferably all data source devices) and then perform the installation verification described in the Verification section below. Additional configuration Additional configuration can be performed by logging in to the Profiler GUI and navigating to the Configuration pages. For example, you may want to set up security profile periods as early as possible. The initial Setup page offers the choice of collecting separate traffic profiles for: Weekdays, weeknights, and weekends, or Weekdays, weekends, Saturdays, and Sundays. If you want to add more profiles or use a different profile scheme, 1. Log in to the Profiler. 2. Go to the Configuration Security Profiles page. 3. Click Reconfigure Weekly Scheme to open the profile scheme composer. 4. Specify the days and times of the traffic collection profiles you want to use. When you specify a new profile scheme, Profiler discards any current baseline information and begins collecting new data. 14

25 Verification Cascade Installation Guide For descriptions of making other configuration changes, refer to the Profiler online help system. Complete the installation by: 1. Verifying Profiler operation. 2. Verifying that the Remote Management Module is accessible. 3. Exiting the installation process. Verifying Profiler operation Verify that the Profiler has been successfully installed and configured by making the following checks. 1. Go to the Dashboard page and verify that the graphs display data. 15

26 2. Go to the System Information page and assure that all status indications (System and Component, DNS Server) are displaying OK. 3. Go to the System Devices/Interfaces page and assure that each data source that is expected to be available is listed and that no status indicators are red. 16

27 4. Go to the Reports Traffic page. Near the bottom of the Report Criteria section, click Run now. Verify that a traffic report is displayed. (It will take a short time for the report to display.) 17

28 Verifying Remote Management Module access Verify that the RMM can be accessed as follows: 1. Point your browser to the IP address that you specified for the RMM on the Setup page during the Configuration task. For example, This displays the RMM login page. 2. Log in to the admin account with the default password password. 3. While logged in to the RMM, you can change the default RMM password and define additional RMM user accounts. A successful login verifies accessibility to the remote management module. Exiting the installation process After verifying that Profiler is receiving and reporting traffic data and its remote management module is accessible over the network, ensure that the responsible person has the IP address, login name, and password of the Profiler and the RMM. This completes the installation process. The Profiler can now be turned over to those who are responsible for setting up user accounts and operational parameters. Refer to the online help system for further configuration procedures. 18

29 5. Enterprise Profiler installation Cascade Installation Guide This section describes the hardware and software configuration necessary to install an Enterprise Profiler. Refer to Section 3 mounting instructions. Configuration information Profiler host name:* Profiler IP address:* Netmask:* Default gateway:* When you configure the Profiler, you will be asked to provide configuration information. Information that is required to complete the installation is listed in the table that follows with an asterisk (*). Items not marked with an asterisk are optional during installation and can be specified afterwards on the Profiler Configuration General Settings page if necessary. It may be useful to write the configuration values in the blank column of the table so that you can refer to them during the configuration step or afterward. DNS name resolution for hosts (enable or disable): Primary DNS server IP address: Secondary DNS IP address: DNS search domain: NTP server IP addresses:* Applies only if Profiler is being synchronized to an external NTP server. Enter one or more addresses as a comma-separated list. Time Zone: Flow encryption certificate (default or new certificate): For faster installation, use the default encryption certificate shipped with the Profiler and then generate a new certificate later. Profiler Management Module IP address: * If you will be changing from the default address of This setting was previously called the Management address. 19

30 Profiler Database Module IP address: * If you will be changing from the default address of Profiler Expansion Module 1 IP address: * If you will be changing from the default address of This setting was previously called the mblade1 address. Profiler Expansion Module 2 IP address: * SNMP information: Profiler is set by default to use SNMP Version 1 and the community name mazu (all lowercase) to allow MIB browsing. If configuring SNMP at this time, obtain the necessary V1 or V3 information. Outgoing mail server name, port number, and From address. Applies only if you will be specifying a server that Profiler is to use for sending reports or alert notifications. Inside addresses: IP addresses or address ranges of hosts that the Profiler is to track individually. The default values are 10/8,172.16/12, /16. Security Profile settings:* You can use either three traffic collection profiles (weekdays, weeknights, and weekends) or four (weekdays, weeknights, Saturdays, and Sundays). After installation, you can define others. You can also specify the times when weekdays begin and end (default times are 9:00 am to 5:00 pm). NAS setup (IP address*, partition name*, directory name, and partition size*): Applies only if you are using a NAS device and are not using the default Profiler settings. Password to use for your initial Profiler login:* The default password admin. New password to enter when prompted to change the initial Profiler password:* Remote Management Module IP address Remote Management Module netmask Remote Management Module gateway 20

31 Service Management Leave this set to ByLocation unless you are requested to choose another group type for service locations. Configuring the Enterprise Profiler After the Enterprise Profiler modules are mounted and have been powered on for more than two minutes, you can configure them using the Profiler web GUI. All Enterprise Profiler modules must be on the same network so that they can communicate with one another at their default addresses. You assign the operational addresses by accessing the Management Module and entering the addresses. The Management Module uses the default addresses of the other modules to connect to them and to change their addresses to the ones you have specified. The RMM in the Management Module can be configured using the Profiler web GUI. However, the RMMs in the other Profiler Modules must be configured by connecting directly to those chassis. Configuring the Management Module The first time you log in to a newly-installed system, it displays an initial Setup page. This is a one-time display. After you set up the initial configuration, you can make subsequent configuration changes on the Configuration pages of the GUI. To configure the Enterprise Profiler, you need a PC on the network to which you have connected the modules. The PC must be running Mozilla Firefox or Microsoft Internet Explorer. It must have an Ethernet port configured for TCP/IP networking and an IP address that does not conflict with the default IP addresses of the Profiler modules. For example, the LAN interface adapter settings of this PC can be set to: IP Address: Network mask: Gateway: Using these settings, connect to the Profiler Management Module as follows: 1. On the management network, point your browser to This displays the Profiler login page. 2. Log in with the default user name admin and the default password admin (unless you arranged with Riverbed for a unique user name and password). This displays the Setup page. 21

32 3. Fill in all the required fields (marked with an asterisk) on the Setup page. 22

33 4. In the RMM Settings section, click Set up RMM. This opens a setup page. 5. Enter the factory preset username admin and password password in the setup popup. 6. Enter the RMM network interface IP address, netmask and gateway and click OK. 7. Check to ensure that the new RMM address information is displayed in the RMM Settings section. 8. At the bottom of the Setup page, there is a checkbox labeled Power down after configuration. This is provided for situations in which someone configures the Enterprise Profiler in a staging area and then subsequently moves it to another area. If the Profiler is mounted in the rack and connected to the network on which you will be using it, leave the Power down after configuration box unselected and click Configure Now. If the Profiler must be powered off, remounted, and reconnected before it is deployed, select the Power down after configuration box and click Configure Now. 9. When you click Configure Now, you will be prompted to change the password. The password you enter here must be the one you will use after this point in the procedure. Enter your new password. Configuring Remote Management Modules To configure the RMMs in the Database Module and Expansion Modules, 1. Disconnect the laptop you used to configure the Management Module from the network. 2. Using a crossover cable, connect it to the RMM connector on the Database Module. 23

34 Additional configuration 3. Point your browser to This displays the RMM login page. 4. Log in with the default user name admin and the default password password (unless you arranged with Riverbed for a unique user name and password). This displays the main page of the RMM web GUI. 5. Change the RMM address information as necessary. 6. Log out of the RMM, remove the crossover cable, and connect the straight-through cable from the management network. 7. Repeat these steps for the Expansion Module(s). Additional configuration can be performed by logging in to the Profiler GUI and navigating to the Configuration pages. For example, the Setup page offers the choice of collecting separate traffic profiles for: Weekdays, weeknights, and weekends, or Weekdays, weekends, Saturdays, and Sundays. If you want to add more profiles or use a different profile scheme, 1. Log in to the Profiler. 2. Go to the Configuration Security Profiles page. 3. Click Reconfigure Weekly Scheme to open the profile scheme composer. 4. Specify the days and times of the traffic collection profiles you want to use. When you specify a new profile scheme, Profiler discards any current baseline information and begins collecting new data. For descriptions of making other configuration changes, refer to the Profiler online help system. 24

35 Verification Complete the installation by: 1. Verifying Profiler operation. 2. Verifying that the Remote Management Modules are accessible. 3. Exiting the installation process. Verifying Profiler operation Verify that the Profiler has been successfully installed and configured by making the following checks. 1. Go to the Dashboard page and verify that the graphs display data. 25

36 2. Go to the System Information page and assure that all status indications (System, Component and DNS Server) are displaying OK. 26

37 3. Go to the System Devices/Interfaces page and assure that each data source that is expected to be available is listed and that no status indicators are red. 4. Go to the Reports Traffic page. Near the bottom of the Report Criteria section, click Run now. Verify that a traffic report is displayed. (It will take a short time for the report to display.) Verifying Remote Management Module access Verify that the RMMs can be accessed as follows: 1. On the network on which the RMMs are connected, point your browser to the IP address that you specified for the Management Module RMM on the Setup page during the Configuration task. For example, This displays the RMM login page. 27

38 2. Log in to the admin account with the default password password (unless you arranged for the system to be shipped with a different password). 3. While logged in to the RMM, you can change the default RMM password and define additional RMM user accounts. 4. Log out of the Management Module RMM and log in to the Data Module RMM at the IP address that you set up during the RMM configuration task. A successful login verifies accessibility to the remote management module. 5. Log in to each Expansion Module RMM to ensure that each is accessible over the network. Exiting the installation process After verifying that the Enterprise Profiler is receiving and reporting traffic data and its remote management modules are accessible over the network, ensure that the responsible person has the IP address, login name, and password of the Profiler and the RMM. This completes the installation process. The Profiler can now be turned over to those who are responsible for setting up user accounts and operational parameters. Refer to the online help system for further configuration procedures. 28

39 6. Express installation Cascade Installation Guide This section describes the hardware and software configuration necessary to install an Express. Refer to Section 3 mounting instructions. Configuration information Express host name:* Express IP address:* Netmask:* Default gateway:* When you configure the Express, you will be asked to provide configuration information. Information that is required to complete the installation is listed in the table that follows with an asterisk (*). Items not marked with an asterisk are optional during installation and can be specified afterwards on the Configuration General Settings page or other pages if necessary. It may be useful to write the configuration values in the blank column of the table so that you can refer to them during the configuration step or afterward. DNS name resolution for hosts (enable or disable): Primary DNS server IP address: Secondary DNS server IP address DNS search domain: Management interface port settings: 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate Switch port settings: The settings of the switch port or hub that the Express management port connects to. Monitored network port settings mon0 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate As required by the tap or mirror port on the monitored network. Does not apply to flow-monitoring-only models. 29

40 Monitored network port settings mon1 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate As required by the tap or mirror port on the monitored network. Does not apply to flow-monitoring-only models. Packet Deduplication Enable packet deduplication if your network configuration might cause the Cascade appliance to see duplicated packets. NTP server IP addresses:* Applies only if Express is being synchronized to an external NTP server. Enter one or more addresses as a comma-separated list. Time Zone: NetFlow port: Applies only if Express is receiving NetFlow data (versions 1, 5, 7 or 9) or IPFIX data. See Note 1 below. sflow port: Applies only if Express is receiving sflow data (versions 2, 4 or 5). See Note 1 below. Packeteer port: Applies only if Express is receiving Packeteer Flow Detail Records (versions 1 or 2). See Note 1 below. SNMP information: Express is set by default to use SNMP Version 1 and the SNMP community name mazu (all lowercase) to allow MIB browsing. If you are configuring SNMP at this time, obtain the necessary V1 or V3 information. Outgoing mail server name, port number, and From address. Applies only if you will be specifying a server that Express is to use for sending reports or alert notifications. Inside addresses: IP addresses or address ranges of hosts that the Express is to track individually. 30

41 Security Profile settings:* You can use either three traffic collection profiles (weekdays, weeknights, and weekends) or four (weekdays, weeknights, Saturdays, and Sundays). After installation, you can define others. You can also specify the times when weekdays begin and end (default times are 9:00 am to 5:00 pm). Password to use for your initial Express login:* The default password admin. New password to enter when prompted to change the initial Express password:* Applies only to systems not previously configured. Remote Management Module IP address Remote Management Module netmask Remote Management Module gateway Service Management Leave this set to ByLocation unless you are requested to choose another group type for service locations. Note 1: Do not send more than one type of flow data to the same port. Configuring the Express The first time you log in to a newly-installed system, it displays an initial Setup page. This is a one-time display. After you set up the initial configuration, you can make subsequent configuration changes on the Configuration pages of the GUI. To configure the Express, you need a separate PC and a crossover cable. This PC must have an Ethernet port configured for TCP/IP networking. It must also be running Mozilla Firefox or Microsoft Internet Explorer. The LAN interface adapter settings of this PC must be set to: IP Address: Network mask: Gateway:

42 Using these settings, connect to the Express as follows: 1. Use a crossover Ethernet cable to connect the Ethernet port of your PC to the Management connector on the left rear of the Express. 2. Point your browser to This displays the login page. 3. Log in with the default user name admin and the default password admin This displays the Setup page. 32

43 4. Fill in all the required fields (marked with an asterisk) on the Setup page. 5. In the RMM Settings section, click Set up RMM. This opens a setup page. 6. Enter the factory preset username admin and password password in the setup popup. 33

44 7. Enter the RMM network interface IP address, netmask and gateway and click OK. 8. Check to ensure that the new RMM address information is displayed in the RMM Settings section. 9. At the bottom of the Setup page, there is a checkbox labeled Power down after configuration. If the Express is mounted in the rack and you are ready to connect it to the network, leave the Power down after configuration box unselected and click Configure Now. If the Express must be powered off and mounted in the rack before it can be connected to the network, select the Power down after configuration box and click Configure Now. 10. When you click Configure Now, you will be prompted to change the password. The password you enter here must be the one you will use after this point in the procedure. Enter your new password. 11. When the password change operation is completed, exit from the browser session and disconnect the crossover cable from the Express. Additional configuration tasks, such as specifying a traffic collection profile scheme that is not available on the Setup page, can be performed by logging in to the Express GUI after it is connected to the management network. If the Express is mounted in the rack and ready to connect to the network, proceed to the next section, Network connections. If the Express still needs to be mounted, wait for it to power down and then mount it in the rack as described in Section 3, Mounting and powering, before proceeding to the next section. 34

45 Network connections After the Express is mounted, configured, and has been powered on for more than two minutes, connect the network cable and verify the connections as follows: 1. Connect the cable from your network to the Management connector on the left rear of the Express. This is the same connector that you used to configure the Express. 2. If your Express is a flow-monitoring-only model, skip to Step 3 below. If your Express is not a flow-monitoring-only model, then connect the cables from the tap or mirror ports on the monitored networks to the network monitoring ports, which are labeled Mon0 and Mon1. 3. Connect a cable from the network to the RMM connector on the right rear of the Express. The RMM connection and the Express management connection can be on different subnets, but these must correspond to the addresses you assigned for each interface on the Setup page. 4. Point your browser to the Express IP address that you specified on the Setup page during the Configuration task. This displays the login page. 35

46 5. Log in to the admin account with the password you specified at the end of the configuration task. 6. Navigate to the System Devices/Interfaces page and check the status of the data source devices on the Devices tab. When a data source comes on line, the Express begins collecting data. At least one data source must be listed with a green status indicator before you can complete the Express installation verification step. If no data sources are listed on the System Devices/Interfaces page Devices tab, then Express installation and configuration cannot be verified. Set up at least one data source device (preferably all data source devices) and then perform the installation verification described in the Verification section below. Additional configuration Additional configuration can be performed by logging in to the Express GUI and navigating to the Configuration pages. For example, you may want to set up security profile periods as early as possible. The initial Setup page offers the choice of collecting separate traffic profiles for: Weekdays, weeknights, and weekends, or Weekdays, weekends, Saturdays, and Sundays. If you want to add more profiles or use a different profile scheme, 1. Log in to the Express. 2. Go to the Configuration Security Profiles page. 3. Click Reconfigure Weekly Scheme to open the profile scheme composer. 36

47 Verification 4. Specify the days and times of the traffic collection profiles you want to use. When you specify a new profile scheme, Express discards any current baseline information and begins collecting new data. For descriptions of making other configuration changes, refer to the Profiler help system. Complete the installation by: 1. Verifying Express operation. 2. Verifying that the Remote Management Module is accessible. 3. Exiting the installation process. Verifying Express operation Verify that the Express has been successfully installed and configured by making the following checks. 1. Go to the Dashboard page and verify that the graphs display data. 37

48 38

49 2. Go to the System Information page and assure that all status indications (System and Component, DNS Server) are displaying OK. 39

50 3. Go to the System Devices/Interfaces page and assure that each data source that is expected to be available is listed and that no status indicators are red. 4. Go to the Reports Traffic page. On the Hosts tab, click Run now. Verify that a traffic report is displayed. (It will take a short time for the query to run and the report to display.) 40

51 Verifying Remote Management Module access Cascade Installation Guide Verify that the RMM can be accessed as follows: 1. Point your browser to the IP address that you specified for the RMM on the Setup page during the Configuration task. For example, This displays the RMM login page. 2. Log in to the admin account with the default password password (unless you arranged for the system to be shipped with a different password). 3. While logged in to the RMM, you can change the default RMM password and define additional RMM user accounts. A successful login verifies accessibility to the remote management module. Exiting the installation process After verifying that Express is receiving and reporting traffic data and its remote management module is accessible over the network, ensure that the responsible person has the IP address, login name, and password of the Express and the RMM. This completes the installation process. The Express can now be turned over to those who are responsible for setting up user accounts and operational parameters. Refer to the online help system for further configuration procedures. 41

52 7. Sensor installation This section describes the hardware and software configuration necessary to install a Sensor. Refer to Section 3 mounting instructions. Configuration information Sensor host name:* Sensor IP address:* Netmask:* Default Gateway:* When you configure the Sensor, you will be asked to provide configuration information. Information that is required to complete the installation is listed with an asterisk (*) in the table that follows. Items not marked with an asterisk are optional during installation and can be specified afterwards on the Sensor Configuration General Settings page if necessary. It may be useful to write the configuration values in the blank column of the table so that you can refer to them during the configuration step or afterward. DNS name resolution for hosts (enable or disable): Primary DNS server IP address: Secondary DNS server IP address: DNS search domain: Management interface port settings: 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate Switch port settings: The settings of the switch port or hub that the Sensor management port connects to. Monitored network port settings mon0 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate As required by the tap or mirror port on the monitored network. Does not apply to Sensors with 10 Gbps interfaces. 42

53 Monitored network port settings mon1 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate As required by the tap or mirror port on the monitored network. Does not apply to Sensors with 10 Gbps interfaces. Monitored network port settings mon2 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate As required by the tap or mirror port on the monitored network. Monitored network port settings mon3 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate As required by the tap or mirror port on the monitored network. Packet Deduplication Enable packet deduplication if your network configuration might cause the Cascade appliance to see duplicated packets. Time Zone: Flow encryption certificate (default or new certificate): For faster installation, use the default encryption certificate shipped with the Sensor and then generate a new certificate later. SNMP information: Sensor is set by default to use SNMP Version 1 and the SNMP community name mazu (all lowercase) to allow MIB browsing. If you are configuring SNMP at this time, obtain the necessary V1 or V3 information. First Profiler data input address:* The address of the Profiler to which the Sensor will send traffic data. This is the IP address of the management interface of an Express or Standard Profiler or the address of the first Expansion Module for an Enterprise Profiler. Second Profiler data input address: If the Sensor will be sending traffic data to more than one Profiler, this is the IP address of the second Profiler (management interface of an Express or Standard Profiler or the address of the first Expansion Module for an Enterprise Profiler). Third Profiler data input address: Fourth Profiler data input address: 43

54 Fifth Profiler data input address: Password to use for your initial Sensor login:* The default password admin. New password to enter when prompted to change the initial Sensor password:* Applies only to systems not previously configured. Remote Management Module IP address Remote Management Module netmask Remote Management Module gateway Configuring the Sensor The first time you log in to a newly-installed system, it displays an initial Setup page. This is a one-time display. After you set up the initial configuration, you can make subsequent configuration changes on the Configuration pages of the GUI. To configure the Sensor, you need a separate PC and a crossover cable. This PC must have an Ethernet port configured for TCP/IP networking. It must also be running Mozilla Firefox or Microsoft Internet Explorer. The LAN interface adapter settings of this PC must be set to: IP Address: Network mask: Gateway: Using these settings, connect to the Sensor as follows: 1. Use a crossover Ethernet cable to connect the Ethernet port of your PC to the Management connector on the left rear of the Sensor. 44

55 2. Point your browser to This displays the login page. 3. Log in with the default user name admin and the default password admin (unless you arranged with Riverbed for a unique user name and password). This displays the Sensor Setup page. 4. Fill in all the required fields (marked with an asterisk) on the Setup page. 45

56 5. In the RMM Settings section, click Set up RMM. This opens a setup page. 6. Enter the factory preset username admin and password password in the setup popup. 7. Enter the RMM network interface IP address, netmask and gateway and click OK. 8. Check to ensure that the new RMM address information is displayed in the RMM Settings section. 9. At the bottom of the Setup page, there is a checkbox labeled Power down after configuration. If the Sensor is mounted in the rack and you are ready to connect it to the network, leave the Power down after configuration box unselected and click Configure Now. If the Sensor must be powered off and mounted in the rack before it can be connected to the network, select the Power down after configuration box and click Configure Now. 10. When you click Configure Now, you will be prompted to change the password. The password you enter here must be the one you use after this point in the procedure. Enter your new password. 11. When the password change operation is completed, exit from the browser session and disconnect the crossover cable from the Sensor. Additional configuration tasks, such as specifying the Profilers to which the Sensor is to send data, can be performed by logging in to the Sensor GUI after it is connected to the management network. If the Sensor is mounted in the rack and ready to connect to the network, proceed to the next section, Network connections. If the Sensor still needs to be mounted, wait for it to power down and then mount it in the rack as described in Section 3, Mounting and powering, before proceeding to the next section, Network connections. 46

57 Network connections After the Sensor is mounted, configured, and has been powered on for more than two minutes, connect the network cable and verify the connections as follows: 1. Connect the cable from your management network to the Management connector on the rear of the Sensor. This is the same connector that you used to configure the Sensor. 2. Connect the cables from the taps or mirror ports on the monitored networks to the Sensor network monitoring ports, which are labeled Mon0, Mon1,. The number and type of monitor connectors depend on the Sensor model. 3. Connect a cable from the network to the RMM connector on the right rear of the Sensor. The RMM connection and the Sensor management connection can be on different subnets, but these must correspond to the addresses you assigned for each interface on the Setup page. 47

58 4. Point your browser to the Sensor IP address that you specified on the Sensor Setup page during the Configuration task. This displays the login page. 5. Log in to the admin account with the password you specified at the end of the Configuration task. 6. Navigate to the System Information page and confirm that the System status is OK. Additional configuration Additional configuration, such as specifying which Profilers are to receive data from the Sensor, can be performed on the Configuration pages. To specify Profilers that are to receive traffic data from the Sensor: 1. Go to the Configuration Profilers page. 48

59 2. Click Add New Entry to open a blank entry for specifying a destination Profiler. 3. In the Profiler IP Address box, enter the IP address of the management interface for an Express or Standard Profiler, or the address of the first Expansion Module for an Enterprise Profiler. 4. Click Configure Now at the bottom of the page to apply the settings. Verification For descriptions of making other configuration changes, refer to the Sensor online help system. Complete the installation by: 1. Verifying Sensor operation. 2. Verifying that the Remote Management Module is accessible. 3. Exiting the installation process. Verifying Sensor operation Verify that the Sensor has been successfully installed and configured by logging in and checking the Overview page. The Overview page should show traffic information about the monitored network. 49

60 Verifying Remote Management Module access Verify that the RMM can be accessed as follows: 1. Point your browser to the IP address that you specified for the RMM on the Sensor Setup page during the Configuration task. For example, This displays the RMM login page. 2. Log in to the admin account with the default password password (unless you arranged for the system to be shipped with a different password). 3. While logged in to the RMM, you can change the default RMM password and define additional RMM user accounts. A successful login verifies accessibility to the remote management module. Exiting the installation process After verifying that the Sensor is receiving and reporting traffic data and its remote management module is accessible over the network, ensure that the responsible person has the IP address, login name, and password of the Sensor and the RMM. This completes the installation process. The Sensor can now be turned over to those who are responsible for setting up user accounts and operational parameters. Refer to the online help system for further configuration procedures. 50

61 8. Sensor-VE installation Prerequisites Cascade Installation Guide The Sensor-VE is a virtual edition of Sensor that runs on a Riverbed Services Platform (RSP) hosted by a Riverbed Steelhead located at a remote site. It collects traffic data from the LAN interfaces of the Steelhead and sends it to a Riverbed Cascade Profiler. This enables the Profiler to report network performance metrics both before and after the Steelhead optimization. Alternatively, the Sensor-VE can be used to monitor traffic at a remote site using a mirror port or network tap instead of monitoring the Steelhead LAN interfaces. Installation includes the following steps: 1. Ensure that the installation prerequisites are met. 2. Assemble the required configuration information. 3. Ensure RSP is installed and enabled on the Steelhead. 4. Download the Sensor-VE package to the Steelhead (upgrades only). 5. Install Sensor-VE in a RSP Package Slot. 6. Configure and enable the slot. 7. Configure the Sensor-VE management interface. 8. Configure the Sensor-VE monitor interface. 9. Complete the Sensor-VE setup. 10. Verify Sensor-VE operation. 11. Exit the installation process. Ensure that the following prerequisites are met before installing Sensor-VE on the Steelhead: The Steelhead must be running RiOS version 5.5.x or higher. The Steelhead must be running RSP version or higher. The Steelhead must have 12 GB of free disk space and 512 MB of RAM (except for 250 models, which can run with 260 MB of RAM) You must have an administrative account with full read/write privileges on the Steelhead. You must have the license key that was sent to you in when you purchased the Sensor-VE. 51

62 Additionally, the Steelhead should have its SNMP ifindex persistence feature enabled. This is done on the Steelhead CLI. For example: ssh SH> [In this example, the Steelhead is cam-sh12.] cam-sh12 > en cam-sh12 # config t cam-sh12 (config) # snmp ifindex-persist You must restart the optimization service, so that netflow can use the configured ifindex cam-sh12 (config) # exit cam-sh12 # write mem cam-sh12 # show snmp SNMP enabled: yes System location: System contact: Engine ID: 0x b805dc6257f4b328d15 Read-only community: riverbed Traps enabled: yes Interface listen enabled: no Trap interface: primary Persistent ifindex: yes No Listen Interfaces. No trap sinks configured. This helps maintain consistency in interface reporting on the Cascade Profiler or Express that is receiving flow data from the Steelheads. This setting may be impacted when you upgrade your Steelhead software. Configuration information Sensor-VE name: Information that is required to complete the installation is listed with an asterisk (*) in the table that follows. Items not marked with an asterisk can be specified afterwards on the Sensor-VE Configuration General Settings page if necessary. It may be useful to write the configuration values in the blank column of the table so that you can refer to them during the installation or afterward. Sensor-VE management IP address:* Sensor-VE management subnet mask:* Sensor-VE management default gateway IP address:* DNS name resolution for hosts (enable or disable): Primary DNS server IP address: Secondary DNS server IP address: 52

63 DNS search domain: Monitor and collect traffic of the Steelhead AUX port option. Enable this option only if you intend to use the Sensor-VE to monitor a network tap or mirror port connected to the Steelhead Aux connector. Time Zone: Flow encryption certificate (default or new certificate): For faster installation, use the default encryption certificate shipped with the Sensor and then generate a new certificate later. SNMP information: Sensor is set by default to use SNMP Version 1 and the SNMP community name mazu (all lowercase) to allow MIB browsing. If you are configuring SNMP at this time, obtain the necessary V1 or V3 information. Profiler data input address:* The address to which the Sensor-VE will send traffic data. This is the IP address of the management interface of an Express or Standard Profiler or the address of the first Expansion Module for an Enterprise Profiler. New password to enter when prompted to change the default Sensor-VE password:* Verify RSP installation Ensure that the correct version of RSP is installed and enabled on the Steelhead. 1. Log into the Steelhead user interface using an account that has full read/write privileges. 53

64 2. Go to the Configure > Branch Services > RSP Service page. 3. Verify that: RSP version 5.5 or higher is installed Free disk space is 12 GB or higher Free memory meets the minimum requirements listed in the table below. New Systems Free Memory (Megabytes) Upgraded Systems RSP is running Download the Sensor-VE package to the Steelhead (upgrades only) New Steelhead appliances that were ordered with the RSP option may include the Sensor-VE package. You can see if the Sensor-VE package is already loaded by navigating to the Configure > Branch Services > RSP Packages page and looking in the Packages section. If the Sensor-VE package is already loaded, skip to the next procedure ( Install Sensor-VE in a RSP Package Slot ). If it is not loaded, you must download the package file from the Riverbed Support site. The URL for this site is included with the license key in your purchase confirmation . 54

65 To download the Sensor-VE package or to confirm that it is present: 1. Go to the Configure > Branch Services > RSP Packages page. 2. In the Packages section, click Add Package if it is not already expanded. 3. If the Sensor-VE package is listed in the Packages section, skip the next procedure. If it is not present, then select From URL and enter the download URL from your purchase confirmation Download the Sensor-VE package by clicking Add Package. Note: Do not navigate away from this page until the download completes. Install Sensor-VE in an RSP Package Slot 1. Go to the Configure > Branch Services > RSP Packages page. 2. In the Slots: section, click an available slot number to expand the entry. 3. Select Sensor-VE package name in section the Package field of the expanded slot display. 4. Assign the slot name that you would like displayed for the package, such as Sensor-VE. 55

66 5. Click Install to unpack and mount the Sensor-VE image in the slot. This may require 10 minutes or more. Do not navigate away from this page until the installation operation completes. Configure and enable the slot Configure the virtual platform so that Sensor-VE has access to the network and is running with the correct memory limit. 1. Go to the Configure > Branch Services > RSP Packages page. 2. In the Slots: section, click the name or number for the slot in which the Sensor-VE is installed. This expands the entry. 3. In the Memory Footprint field, specify the number of megabytes of memory to be allocated to the Sensor-VE, as listed in the table below. New Systems Memory Footprint (Megabytes) Upgraded Systems

67 4. In the Management Virtual Network Interfaces section: Assign the Sensor-VE aux virtual interface to the Steelhead aux physical interface. Assign the Sensor-VE ctl virtual interface to the Steelhead primary physical interface. 5. Click Update Slot and wait for the display to refresh. 6. When the slot update operation completes, click Enable Slot. This starts the Sensor-VE software. Configure the Sensor-VE monitor interfaces Traffic from each Steelhead LAN interface-to-wan interface traffic path (e.g., inpath0_0) must be copied to a corresponding Sensor-VE monitor interface (e.g., mon0). The Sensor-VE must monitor traffic right at the start of the path, at the LAN interface. 1. Go to the Configure > Branch Services > RSP Data Flow page for the first Steelhead LAN-to-WAN data path. For example, navigate to: Configure > Branch Services > RSP Data Flow inpath0_0 2. Click Add a VNI to expand the display. 3. In the Interface list box, select the first Sensor-VE monitor interface (e.g., Sensor-VE:mon0). 4. In the Data Flow Position list box, select Start to place the Sensor-VE monitor interface closest to the Steelhead LAN interface in the data flow. 5. Click Add to assign the first virtual network interface of the Sensor-VE to the first position in the data flow path. 57

68 6. After the operation completes, click the name of the Sensor-VE monitor interface (e.g., mon0) in the VNI Name column to display the details of the connection. 7. Ensure that all data flow rules options are set to all. The Sensor-VE should monitor all traffic on the Steelhead LAN interfaces. 8. Ensure that both the Default IP Policy and the Default Non-IP Policy lists have the Copy Traffic to Slot option selected. 9. Click Apply to complete the assignment for this interface and close the details window. 10. If the Steelhead has more than one LAN interface, then repeat this procedure for each LAN interface. For example, navigate to: Configure > Branch Services > RSP Data Flow inpath0_1 and continue with Step 2 above. Configure the Sensor-VE management interface Use RSP to specify the network address at which the Sensor-VE user interface can be reached. 1. If you are not still on the Configure > Branch Services > RSP Packages page, then go to that page and, in the Slots: section, click the name or number for the slot in which the Sensor-VE is installed to expand the entry. 58

69 2. Near the bottom of the slot configuration display, click Launch VM Console. This opens a new window. If you are notified that your browser does not have the necessary VMware plug-in, load the plug-in and try again. 3. At the login prompt, log in to the VMware component using the default account. The password for this account is the same as the Steelhead CLI admin password. The default password is password. Login: admin Password: password 4. Click in the VMware window to launch the VMware Remote Console for the Sensor-VE. 5. Click in the Sensor-VE console window to make it the active window. (Use Ctrl + Alt to exit from the console window when necessary.) 59

70 6. When prompted to log in to the Sensor-VE, use: Login: admin Password: admin 7. When you are asked to continue, click Yes and answer the questions. You will be prompted to enter the network address for reaching the Sensor- VE and the address of the Profiler to which the Sensor-VE is to send data. Additionally, you will be asked for your Sensor-VE license key, which was included in the purchase confirmation . You can enter the license key later, if necessary, but you must enter the IP address at this time. The dialog will appear similar to the following: 8. After answering the configuration questions, confirm that the setup information is correct. This causes the Sensor-VE to reboot. When the Sensor-VE has finished rebooting, you can close the remote console window. (Use Ctrl + Alt to exit from the console window to your main window.) Complete the Sensor-VE setup To configure the Sensor-VE, 1. Point your browser to the Sensor-VE IP address that you assigned to the Sensor-VE management interface in the remote console window. Log in using the default account: Login: admin Password: admin 60

71 2. The first time you log in to a newly-installed system, it displays an initial Setup page. This is a one-time display. After you set up the initial configuration, you can make subsequent configuration changes on the Configuration pages of the GUI. 3. Check the entries on the Setup page. 4. If you will be using the Sensor-VE to monitor traffic from a network tap or mirror port (such as a SPAN port on a switch or router), then select the Monitor and collect traffic on the Steelhead Aux port option in the Monitor Interface Configuration section. Otherwise, this option should not be selected. See the note below for additional requirements. 5. When you click Configure Now, you will be prompted to change the password. The password you enter here must be the one you use after this point in the procedure. Enter your new password. 61

72 6. When the password change operation is completed, the browser session terminates. Wait a few minutes for the configuration changes to be made and then login in using the new password. Additional configuration tasks can be performed by logging in to the Sensor-VE from anywhere on the management network. Note: To use the Steelhead Aux port, ensure that it is enabled on the Steelhead. Go to the Steelhead Configure > Networking > Base Interfaces page and select Enable Aux Interface in the Auxiliary Interface section. 62

73 Network connections The connections between the Steelhead LAN interfaces and the Sensor-VE monitor interfaces are virtual connections. They were made previously, as part of the software installation. If you are using the Sensor-VE to monitor the Steelhead LAN interfaces, skip ahead to the next section. However, if you use the Sensor-VE to monitor traffic from a network tap or mirror port (such as a SPAN port on a switch or router), then a physical connection is required. Connect a cable from the network tap or the mirror port of the network device to the Aux connector on the Steelhead chassis. To monitor traffic via the Steelhead Aux port, the Sensor-VE must have this source enabled. If you did not already enable it on the Setup page, then you can enable it in the Monitor Interface Configuration section of the Sensor-VE Configuration General Settings page. Verify Sensor-VE operation Verify that the Sensor-VE has been successfully installed and configured by logging in and checking the Overview page. The Overview page should show the Sensor-VE System Status as OK. If the Profiler that is to receive traffic information from the Sensor-VE is online, then the Profiler Status should be shown as OK also. Additionally, the Profiler or Express System Devices/Interfaces page should list the Sensor-VE as a data source. 63

74 Exiting the installation process After verifying that the Sensor-VE is receiving and reporting traffic data, ensure that the responsible person has the IP address, login name, and password. This completes the installation process. The Sensor-VE can now be turned over to those who are responsible for setting up user accounts and operational parameters. Refer to the online help system for further configuration procedures. 64

75 9. Gateway installation Cascade Installation Guide This section describes the hardware and software configuration necessary to install a Gateway. Refer to Section 3 mounting instructions. Configuration information Gateway host name:* Gateway IP address:* Netmask:* Default gateway:* When you configure the Gateway, you will be asked to provide configuration information. Information that is required to complete the installation is listed with an asterisk (*) in the table that follows. Items not marked with an asterisk are optional during installation and can be specified afterwards on the Gateway Configuration General Settings page if necessary. It may be useful to write the configuration values in the blank column of the table so that you can refer to them during the configuration step or afterward. DNS name resolution for hosts (enable or disable): Primary DNS server IP address: Secondary DNS server IP address: DNS search domain: Management interface port settings: 10/100/1000 Mb/s, half- or full-duplex, or auto-negotiate Switch port settings: The settings of the switch port or hub that the Gateway management port connects to. Time Zone: Flow encryption certificate (default or new certificate): For faster installation, use the default encryption certificate shipped with the Gateway and then generate a new certificate later. 65

76 Data Sources Use NetFlow Specify the port number on which the Gateway will receive the data. Applies only if the Gateway is receiving NetFlow data (versions 1, 5, 7 or 9), IPFIX, or cflow data. See Note 1 at the end of this table. Data Sources Use sflow Specify the port number on which the Gateway will receive the data. Applies only if the Gateway is receiving sflow data (versions 2, 4 or 5). See Note 1 at the end of this table. Data Sources Use Packeteer Specify the port number on which the Gateway will receive the data. Applies only if the Gateway is receiving Packeteer Flow Detail Records (versions 1 or 2). See Note 1 at the end of this table. SNMP information: The Gateway is set by default to use SNMP Version 1 and the SNMP community name mazu (all lowercase) to allow MIB browsing. If you are configuring SNMP at this time, obtain the necessary V1 or V3 information. First Profiler data input address. The address of the Profiler to which the Gateway will send traffic data. This is the IP address of the management interface of an Express or Standard Profiler or the address of the first Expansion Module (mblade 1) for an Enterprise Profiler. If data sent to this Profiler is to be limited to only data received from certain flow sources, then specify those sources. Second Profiler data input address. If the Gateway will be sending traffic data to more than one Profiler, this is the IP address of the second Profiler (management interface of an Express or Standard Profiler or the address of the first Expansion Module for an Enterprise Profiler). If flow forwarding to this Profiler is to be limited to only data received from certain flow sources, then specify those sources. Third Profiler data input address Profiler IP address: Flow sources: Profiler IP address: Flow sources: Profiler IP address: Flow sources: 66

77 Fourth Profiler data input address Profiler IP address: Flow sources: Fifth Profiler data input address Profiler IP address: Flow sources: Data Forward Destination 1 IP address and port number of the first destination to which the Gateway is to forward flow data, the type of data (e.g., NetFlow) to be forwarded, and whether or not the source address of the forwarded packets should be overwritten with the source address from which they were received. If flow forwarding to this destination is to be limited to data received from only certain flow sources, then specify those sources. Data Forward Destination 2 Data Forward Destination 3 IP address: Port: Type: Source: Overwrite source address? Yes/No: IP address: Port: Type: Source: Overwrite source address? Yes/No: IP address: Port: Type: Source: Overwrite source address? Yes/No: 67

78 Data Forward Destination 4 Data Forward Destination 5 IP address: Port: Type: Source: Overwrite source address? Yes/No: IP address: Port: Type: Source: Overwrite source address? Yes/No: Password to use for your initial Gateway login:* The default password admin. New password to enter when prompted to change the initial Gateway password:* Applies only to systems not previously configured. Remote Management Module IP address Remote Management Module netmask Remote Management Module gateway Note 1: Do not send more than one type of flow data to the same port. 68

79 Configuring the Gateway The first time you log in to a newly-installed system, it displays an initial Setup page. This is a one-time display. After you set up the initial configuration, you can make subsequent configuration changes on the Configuration pages of the GUI. To configure the Gateway, you need a separate PC and a crossover cable. This PC must have an Ethernet port configured for TCP/IP networking. It must also be running Mozilla Firefox or Microsoft Internet Explorer. The LAN interface adapter settings of this PC must be set to: IP Address: Network mask: Gateway: Using these settings, connect to the Gateway as follows: 1. Use a crossover Ethernet cable to connect the Ethernet port of your PC to the Management connector on the left rear of the Gateway. 2. Point your browser to This displays the login page. 3. Log in with the default user name admin and the default password admin (unless you arranged with Riverbed for a unique user name and password). This displays the Gateway Setup page. 4. Fill in all the required fields (marked with an asterisk) on the Setup page. 69

80 5. In the RMM Settings section, click Set up RMM. This opens a setup page. 6. Enter the factory preset username admin and password password in the setup popup. 7. Enter the RMM network interface IP address, netmask and gateway and click OK. 70

81 8. Check to ensure that the new RMM address information is displayed in the RMM Settings section. 9. At the bottom of the Setup page, there is a checkbox labeled Power down after configuration. If the Gateway is mounted in the rack and you are ready to connect it to the network, leave the Power down after configuration box unselected and click Configure Now. If the Gateway must be powered off and mounted in the rack before it can be connected to the network, select the Power down after configuration box and click Configure Now. 10. When you click Configure Now, you will be prompted to change the password. The password you enter here must be the one you use after this point in the procedure. Enter your new password. 11. When the password change operation is completed, exit from the browser session and disconnect the crossover cable from the Gateway. Additional configuration, such as specifying Profilers that are to receive data from the Gateway and forwarding flow data from particular sources to particular Profiler destinations, can be performed by logging in to the Gateway GUI after it is connected to the management network. If the Gateway is mounted in the rack and ready to connect to the network, proceed to the next section, Network connections. If the Gateway still needs to be mounted, wait for it to power down and then mount it in the rack as described in Section 3, Mounting and powering section before proceeding to the next section, Network connections. Network connections After the Gateway is mounted, configured, and has been powered on for more than two minutes, connect the network cable and verify the connection as follows: 1. Connect the cable from your management network to the Management connector on the rear of the Gateway. This is the same connector that you used to configure the Gateway. 71

82 2. Connect a cable from the network to the RMM connector on the right rear of the Gateway. The RMM connection and the Gateway management connection can be on different subnets, but these must correspond to the addresses you assigned for each interface on the Setup page. 3. Point your browser to the IP address specified on the Setup page during the Configuration task. This displays the login page. 4. Log in to the admin account with the password you specified at the end of the Configuration task. 5. Navigate to the System Information page. 6. Confirm that the System status is OK. 72

83 Additional configuration Additional configuration, such as specifying Profilers that are to receive data from the Gateway and forwarding flow data from particular sources to particular Profiler destinations, can be performed on the Configuration pages. For descriptions of making other configuration changes, refer to the Gateway online help system. Identifying Profilers To specify Profilers that are to receive traffic flow data from the Gateway: 1. Go to the Configuration Profilers page. 2. Click Add New Entry to open a blank entry for specifying a destination Profiler. 3. In the Profiler IP Address box, enter the IP address of the management interface for an Express or Standard Profiler, or the address of the first Expansion Module for an Enterprise Profiler. 4. In the Flow Sources box, either: Leave the box blank to forward all flow data to the specified Profiler, or Enter a comma-separated list of the IP addresses of flow source devices whose traffic is to be sent to the Profiler. You can enter IP addresses by clicking Browse and searching for the flow source device by name, address, or subnet. 5. Click Configure Now at the bottom of the page to apply the settings. Flow forwarding Gateway can forward flow data to up to five destinations. Flow data is forwarded in the format in which it is received. You can make the forwarded flow data appear to be coming from the Gateway. Use the Overwrite Source option to use the Gateway address as the source address in the forwarded data packets. This may be necessary to prevent packets from appearing to be spoofed. 73

84 To specify forwarding destinations, 1. Go to the Configuration Flow Forwarding page. Verification 2. Click Add New Entry to open a blank entry for specifying a destination Profiler. 3. Enter the destination IP address, port number, and data type for each destination. (For IPFIX data, select NetFlow.) 4. If you need to have the data identified as coming from the Gateway, select Overwrite Source to use the Gateway address as the source address in the forwarded data packets. 5. In the Flow Sources box, either: Leave the box blank to forward all flow data to the specified device, or Enter a comma-separated list of the IP addresses of flow source devices whose traffic is to be sent to the specified destination device. You can enter IP addresses by clicking Browse and searching for the flow source device by name, address, or subnet. 6. Click Configure Now at the bottom of the page to apply the settings. The Gateway begins forwarding flow data to the destination devices within 5 minutes after you click Configure Now. Complete the installation by: 1. Verifying Gateway operation. 2. Verifying that the Remote Management Module is accessible. 3. Exiting the installation process. Verifying Gateway operation Verify that the Gateway has been successfully installed and configured by logging in and checking the Overview page. The Overview page identifies all traffic information sources that are currently sending data to the Gateway. Also, it identifies destinations to which the Gateway forwards traffic information. 74

85 If flow sources are currently configured to send data to the Gateway, they should be displayed on the Overview page. If Profilers are receiving data from the Gateway, they should also be displayed on the Overview page. Verifying Remote Management Module access Verify that the RMM can be accessed as follows: 1. Point your browser to the IP address that you specified for the RMM on the Gateway Setup page during the Configuration task. For example, This displays the RMM login page. 2. Log in to the admin account with the default password password (unless you arranged for the system to be shipped with a different password). 3. While logged in to the RMM, you can change the default RMM password and define additional RMM user accounts. A successful login verifies accessibility to the remote management module. Exiting the installation process After verifying that Gateway is receiving and reporting traffic data and its remote management module is accessible over the network, ensure that the responsible person has the IP address, login name, and password of the Gateway and the RMM. This completes the installation process. Refer to the online help system for additional configuration procedures. 75

86 10. SAN installation Introduction This section describes the hardware installation of a Fibre Channel Host Bus Adapter (FC HBA) in a Profiler. Safety Notice Hardware installation involves accessing the inside of the Profiler chassis. To reduce the risk of personal injury or equipment damage, observe the chassis hardware manufacturer s safety warnings and cautions, which are provided in the documentation kit shipped with the Profiler. The Fibre Channel Host Bus Adapter (FC HBA) enables Riverbed Cascade Profiler to access remote storage on a Storage Area Network (SAN) device as if it were a local SCSI disk. This requires you to configure your FC switches or SAN storage devices as necessary to allow connections from Profiler and to assign storage resources to the Profiler. Software configuration requires guidance from Riverbed Support. It is not necessary to configure the software at the time that the hardware is installed. All other Profiler features will function normally without the software for the SAN interface being configured. However, the software must be configured and a SAN device connection must be available in order to verify the installation and operation of this option. Installation involves the following steps: 1. Unpack and inspect the hardware 2. Prepare to install the hardware 3. Install the FC HBA card 4. Prepare to configure the software 5. Contact Riverbed Support for guidance on configuring software Unpacking and inspection 1. If you have ordered SAN options for more than one Profiler, check the shipping documentation to ensure that all components have arrived. 2. Visually inspect the shipment for indications of damage. 3. If any pieces of your order are damaged or missing, contact Riverbed Support before continuing. Phone United States and Canada: Phone outside U.S. and Canada: support@riverbed.com Web: 76

87 Preparing to install the hardware Card mounting considerations The FC HBA is low-profile PCI Express 4 card. It plugs into one of the fullheight PCIe (PCI Express) slots of the Profiler chassis. The WWN (world wide name) of each of the two ports is printed beside the connector. Although these are visible after the card is installed in the chassis, it may be more convenient to record them before installing the card. Cabling considerations The FC HBA card has two 4-Gbps Fibre Channel connectors. The connectors are LC-style for small form factor (SFF) multimode fiber optic cables. They can be connected to a Fibre Channel switch or storage device over the following lengths of cable: Speed (4/2/1 Gbps auto-negotiated) 50/125 μm fiber cable 62.5/125 μm fiber cable Gbps 150 meters 70 meters Gbps 300 meters 150 meters Gbps 500 meters 300 meters Ensure that cables with the correct connectors are available at the Profiler mounting location to connect the FC ports to the SAN device. 77

88 Installing the FC HBA card To install the FC HBA card in the Profiler chassis: 1. Power off the Profiler. The power button is located behind the bezel on the front of the chassis, near the center of the control panel on the upper-right. 2. Unplug all cables and remove the Profiler chassis from the rack. 3. Remove the screw fastening the top cover and remove the top cover. 4. Remove the processor air duct (plastic insert). 5. Remove the PCI riser by lifting the two blue locking latches and then pulling the riser assembly straight up. 6. Locate an empty full-height PCI-e slot in the PCI riser assembly. 7. Insert the FC HBA card in the slot, ensuring that it is seated properly. 8. Reinstall the PCI riser assembly in its original position. Use the latches to lock it in place, making sure it is seated properly. 9. Replace the processor air duct, the top cover, and the top cover screw. 78

89 CAUTION: 10. Reinstall the Profiler in the rack. Observe the safety cautions in the mounting instructions that are shipped with the Profiler. 11. Reconnect the power cable and management network cable. 12. Connect the fiber cable from the SAN device to one of the FC HBA connectors on the rear of the Profiler chassis. 13. Power on the Profiler and reinstall the bezel on the front of the chassis. 14. After 5 minutes, verify that the Link LEDs are lit on both the Profiler FC HBA card and the Fibre Channel device to which it is cabled. At this point, hardware installation is complete and Profiler should be operating normally, although the SAN option will not be operational until the software configuration is completed. Preparing to configure the software All Profiler models include the driver for the SAN interface (Fibre Channel Host Bus Adapter, FC HBA) and the commands necessary to establish a connection with a SAN device. Nothing needs to be downloaded or loaded from disk. Ensure that the following conditions are met and information is available before you begin the software configuration. LUN The SAN administrator must allocate a LUN (logical unit number) for Profiler to use. Note that Profiler will reformat and partition its assigned storage area. Any data on that LUN will be lost unless you specify a command option that prevents Profiler from copying its existing logs to its LUN. WWN The administrator s SAN management solution must associate the LUN with the World Wide Name (WWN) of the Profiler FC HBA port that is to access the SAN device. (The WWN is printed beside the connector.) Login The person performing the software configuration must be able to access the Profiler command line interface and log in to the account named mazu. For an Enterprise Profiler system, they must by able to log in to each Expansion Module. Link The link level connection between Profiler and an FC device must be in operation. This requires only that the Profiler FC HBA is running and cabled to a Fibre Channel device, such as a switch or storage device. 79

90 Schedule Profiler will be off line briefly during the software configuration procedure. If downtime is a consideration, discuss this with Riverbed Support when you set up a time for configuring the software. Contacting Riverbed Support Contact Riverbed Support to discuss and schedule the software configuration. A Riverbed engineer will assist you in configuring the software and verifying that the installation is successful. Also contact Riverbed Support if you would like Riverbed to perform the installation. Phone United States and Canada: Phone outside U.S. and Canada: support@riverbed.com Web: 80

91

92