This paper is a deployment guide for configuring Riverbed Virtual Steelhead (VSH) on the SRE. It begins with some information for new deployments of SRE (especially as it pertains to VSH), then provides some network integration examples. As the virtualization environment is VMware ESXi, this paper will not concentrate on installing VSH on ESXi (please refer to the documentation on the Riverbed Support Site at https://support.riverbed.com/docs/appliance.htm). Instead, this paper will concentrate on the important parts around VSH in this specific ESXi environment: SRE configuration and the various WCCP options. The SRE-V image is a Cisco-prepared version of ESXi. You must use the Cisco version of ESXi on the SRE. This document assumes you have basic understand of ESXi, VSH, and WCCP (as it pertains to Riverbed Steelhead appliances). In this paper, we document the steps we took to get VSH running in the SRE environment. Some of these steps may need to be altered or may not apply in your environment.
mgmt: 10.32.146.217
Router configuration:
interface GigabitEthernet0/3 description mgmt ip address 10.32.146.196 255.255.255.0 duplex auto speed auto !
Make sure you can ping the FTP server from the ISR G2.
mgmt: 10.32.146.217
gi0/3: mgmt 10.32.146.196 Cisco 3945 ISR G2 SRE ESXi 10.1.20.1 sm 4/0 (internal) vmnic1 10.1.20.2
Router configuration:
interface SM4/0 ip address 10.1.20.1 255.255.255.0 service-module ip address 10.1.20.2 255.255.255.0 service-module ip default-gateway 10.1.20.1 !
Figure 4 Configuration of user account with root directory that contains the extracted SRE-V image files
In our test setup, we install the SRE-V infrastructure software on SM4/0 via
Router# service-module sm 4/0 install url ftp://share:share@10.32.146.217/sre-v-k9r.SPA.smv.1.5.1.pkg
Note 1: We hot-plugged a SRE900 module into a 3945-E chassis. After running the install command, the prompt would hang for a few minutes then return. We had to power-cycle the whole chassis to have a successful install. Remember, the installation is done from the router, not from within an SRE console session. The installation process will refer to the pkg file, which will refer it to other files in the same FTP directory. This directory can be the FTP root directory or any subdirectory. The only requirement here is that all of the files from the distribution should be extracted into the same directory. You will have to answer a few questions during the install. The most important one is (on the 900 and 910) decide whether to configure the disks as no raid, RAID0, or RAID1. More on this decision when we discuss performance. If you have any problems during the installation, you can enable logging via:
Router#debug sre-install all
With ESXi now running, you are ready to configure the management IP address for ESXi.
The default login/password for logging into ESXi is root/<no password>. During the SRE-V installation, vmnic1 is automatically assigned the same IP address as what was specified in the servicemodule ip address command (see above). You should still log into the session/console to verify this was done. In the test setup we verified that vmnic1 was chosen for management and already assigned an IP address of 10.1.20.2. Note that in our test setup, 10.1.20.1 is the router side of the SM 4/0 interface. More information on the vmnicX interfaces (including why vmnic1 was selected in our test setup for ESXi management) can be found in the VSH/SRE Network Options section of this document. Once you have logged out of ESXi, close the session via CTRL+ALT+6 then x You will be returned to the router cli. However the session to the ESXi console is still open. To close the session, enter the following command:
Router# service-module sm<slot>/0 session clear
This allows the Windows 2008R2 Server machine to reach the internal network on the SM interface via the management interface of the router (10.32.146.196 on gi0/3).
Figure 5 ESXi network configuration after having added vSwitch2 (mapped to vmnic0/SRE external interface) and a mgmt. network for vmnic1.
We created the mgmt network because the default Managememt Network cannot be mapped to a VSH interface. We can now import the VSH VM/OVA and are able to map the WAN to the SRE-External Interface/vmnic0 and the Primary interface to mgmt/vmnic1.
Even though we are not using the LAN and Aux interface in our test setup, there is currently no way to have VSH interface not assigned to any network. In this case just ignore the warning message. Our test router has 4 Gigabit Ethernet interfaces. gi0/3 is connected to a separate management network, gi0/0 and gi0/1 will each handle LAN and WAN traffic, respectively. We will use the remaining gi0/2 interface as a dedicated interface to connect to the VSH. To do this, we connect a network cable between gi0/2 and the external interface on the SRE. Our new network diagram looks like this:
Windows 2008R2E
mgmt: 10.32.146.217
gi0/3: mgmt 10.32.146.196 Cisco 3945 ISR G2 SRE ESXi 10.1.20.1 sm 4/0 (internal) vmnic1 10.1.20.2 primary 10.1.20.3 VSH
SRE External Interface gi0/2 192.168.4.1 wccp router Figure 7 Adding the WAN and Primary interfaces of VSH to the network topology
Router configuration:
interface GigabitEthernet0/2 ip address 192.168.4.1 255.255.255.0 duplex auto speed auto !
On the VSH, configure the IP addresses and appropriate gateway IP addresses for the Primary and WAN interfaces. Follow the VSH deployment guide instructions on licensing and ESXi resource allocation for your desired VSH model.
mgmt: 10.32.146.217
T1 WAN
Windows 7
P WCC in
VSH
Default branch routing to WAN Let us begin by adding the basic routing needed for the branch to get out to the WAN. gi0/0 is our router LAN interface and gi0/1 is our WAN router interface. The LAN is a flat 192.168.3.0/24 network, and the WAN is a flat 192.168.0.0/24 network. Router configuration:
interface GigabitEthernet0/0 ip address 192.168.3.201 255.255.255.0 duplex auto speed auto
CC W P in
primary 10.1.20.3
10
On the windows machine, configure an IP address on the test network (192.168.3.0/24) and specify the gateway IP address (192.168.3.201). Verify from the Windows client that you can ping the gateway/LAN router interface and the WAN router interface. Basic WCCP configuration (Router) Continue with the WCCP configuration on the router. We will redirect all traffic coming into the router LAN and WAN interfaces to the VSH/external interface on the SRE. The Steelhead will join WCCP group 61. The LAN and WAN interfaces will be configured to redirect traffic coming into those interfaces to WCCP group 61. Router configuration:
ip cef ip wccp 61 ip wccp 62 interface GigabitEthernet0/0 ip address 192.168.3.201 255.255.255.0 ip wccp 61 redirect in duplex auto speed auto ! interface GigabitEthernet0/1 ip address 192.168.0.201 255.255.255.0 ip wccp 61 redirect in duplex auto speed auto !
Note that in this lab example, weve defined WCCP service group 62 but not used it. Since this is a single Steelhead environ ment, in this case having one WCCP service group used is ok, because regardless of the direction of traffic for the single used service group, there is only one WCCP client (Virtual Steelhead) to choose from. In our next example with multiple Steelheads, we will use multiple service groups to load balance to two Virtual Steelheads. Basic WCCP configuration (Steelhead) For a Riverbed primer on WCCP, refer to the Riverbed Deployment Guide on the Riverbed Support Site at https://support.riverbed.com/docs/appliance.htm Here is a summary of basic WCCP configuration used in this environment: Configure > Networking > Simplified Routing: Collect Mappings From: None Configure > Networking > In-Path Interfaces: Set an IP address/default gateway for Inpath0_0 Configure > Optimization > General Service Settings: Enable In-Path Support, Enable L4/PBR/WCCP/Interceptor Support, Enable Optimizations on Interface inpath0_0 Configure > Networking > WCCP: Join appropriate WCCP service groups (a screenshot of this configuration can be seen in the dual VSH WCCP configuration further in this document) Verify you can see the Steelhead as a WCCP client on the router (show ip wccp 61 det). Verify optimization with a remote site. Here is our test setup incorporating a remote site:
11
mgmt: 10.32.146.217
T1 WAN
Windows 7
P WCC in
VSH
CC W P in
primary 10.1.20.3
12
mgmt: 10.32.146.217
T1 WAN
Windows 7
10.1.20.1 WCCP in sm 4/0 (internal) vmnic1 10.1.20.2 sm 4/1 (internal, trunk) vmnic2
C WC P in
VSH
wan0_0 10.1.30.10
vmnic0/primary 10.32.146.243 SRE External Interface SRE ESXi 10.1.40.1 sm 2/0 (internal) vmnic1 10.1.40.2 sm 2/1 (internal, trunk) vmnic2 wan0_0 10.1.30.11 VSH
In this diagram, the red path represents a management network. We use one of the Gigabit ports on the router for management as well as the external interfaces on the SRE (to manage the Steelheads). Management of the ESXi instances is via the internal SRE interface and tied to the SMX/0 interface. This interface is not recommended for user data flow. The green path represents the network path for the customer. On the router, WCCP redirect commands have been applied to the lan and wan interfaces of the router, which are Gi0/0 and Gi0/1, respectively.
13
In this deployment, we SM X/1(mapped to vmnic2, on ESXi) is configured as a trunk to VLAN1. IP addresses cannot be tied to the SM X/1 interfaces. Each VSH WAN interface uses the IP address of VLAN1 as their gateway and WCCP router. Router Configuration ip wccp 61 ip wccp 62 interface GigabitEthernet0/0 description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$$ES_LAN$ ip address 192.168.3.201 255.255.255.0 ip wccp 61 redirect in duplex auto speed auto ! interface GigabitEthernet0/1 ip address 192.168.0.201 255.255.255.0 ip wccp 62 redirect in duplex auto speed auto ! interface GigabitEthernet0/3 description mgmt ip address 10.32.146.196 255.255.255.0 duplex auto speed auto ! interface SM2/0 ip address 10.1.40.1 255.255.255.0 service-module ip address 10.1.40.2 255.255.255.0 !Application: VMware ESXi 4.1.0 build-348481 running on SRE service-module ip default-gateway 10.1.40.1 ! interface SM2/1 description Internal switch interface connected to Service Module switchport mode trunk no ip address ! interface SM4/0 ip address 10.1.20.1 255.255.255.0 service-module ip address 10.1.20.2 255.255.255.0 !Application: VMware ESXi 5.0.0 build-474610 running on SRE service-module ip default-gateway 10.1.20.1 ! interface SM4/1 description Internal switch interface connected to Service Module switchport mode trunk no ip address ! interface Vlan1 ip address 10.1.30.1 255.255.255.0 ip wccp redirect exclude in !
14
The following is the configuration for joining WCCP Service Groups 61 and 62, with 61 expanded:
When configuring WCCP for more than one VSH, make sure to configure Connection Forwarding on each VSH instance. This allows the Steelheads to communicate to make sure each Steelhead gets the proper amount of WCCP bucket allocation (for the Hash assignment scheme). On each VSH instance, go to Configure > Networking > Connection Forwarding, and add each other VSH inpath IP as a neighbor. Enable Connection Forwarding. Enable In-path Neighbor Failure.
15
The following is an example screenshot of Connection Forwarding UI on the SRE 900 configured with the VSH instance on the other SRE (910) as a Neighbor:
Remember, do not use the management network (vmnic1) for user traffic or optimization, to reduce router load.
300 model SRE: as this platform has no hard drive, this is platform is unsupported for VSH. 700/710 model SRE: (Core 2 solo CPU): as this platform has a single core CPU it only supports a V250L/M/H. This platform only has 4GB of RAM. 900/910 model SRE: (Core2 duo CPU): as this platform has a dual core CPU, the highest supported model is a V1050H. This
16
platform has 4 or 8GB of RAM. Since there is a RAM overhead for ESXi, 8GB is required to run the V1050H. Note that ESXi will allow you to configure a VM with more memory than the SRE physically has. For example, an SRE with 4GB of RAM will consume some of that RAM for ESXi itself. This leaves less than 4GB available for a V1050H VSH. However, ESXi will allow you to allocate 4GB to the VM. Doing this will allow the VM to run, and performance may seem good at first. But when VSH attempts to utilize all 4GB of RAM, there is likely to be performance issues as ESXi substitutes slower disk for solid-state RAM. For this reason, allocating more RAM to a VSH than the SRE has is a Riverbed unsupported configuration.
About Riverbed
Riverbed delivers performance for the globally connected enterprise. With Riverbed, enterprises can successfully and intelligently implement strategic initiatives such as virtualization, consolidation, cloud computing, and disaster recovery without fear of compromising performance. By giving enterprises the platform they need to understand, optimize and consolidate their IT, Riverbed helps enterprises to build a fast, fluid and dynamic IT architecture that aligns with the business needs of the organization. Additional information about Riverbed (NASDAQ: RVBD) is available at www.riverbed.com. 2012 Riverbed Technology. All rights reserved. Riverbed, Cloud Steelhead, Granite, Interceptor, RiOS, Steelhead, Think Fast, Virtual Steelhead, CSA, Mazu, Cascade, Cascade Pilot, Shark, AirPcap, Skipware, TurboCap, WinPcap, Wireshark, and Stingray are trademarks or registered trademarks of Riverbed Technology, Inc. in the United States and other countries. Riverbed and any Riverbed product or service name or logo used herein are trademarks of Riverbed Technology. All other trademarks used herein belong to their respective owners. The trademarks and logos displayed herein cannot be used without the prior written consent of Riverbed Technology or their respective owners. Cisco is a registered trademark of Cisco Systems, Inc. and its affiliates in the United States and in other countries. Microsoft is a registered trademark of Microsoft Corporation and its affiliates in the United States and in other countries. VMware is a registered trademark of VMware, Inc. and its affiliates in the United States and in other countries.
Riverbed Technology, Inc. 199 Fremont Street San Francisco, CA 94105 Tel: (415) 247-8800 www.riverbed.com
Riverbed Technology Ltd. One Thames Valley Wokingham Road, Level 2 Bracknell. RG42 1NG United Kingdom Tel: +44 1344 31 7100
Riverbed Technology Pte. Ltd. 391A Orchard Road #22-06/10 Ngee Ann City Tower A Singapore 238873 Tel: +65 6508-7400
Riverbed Technology K.K. Shiba-Koen Plaza Building 9F 3-6-9, Shiba, Minato-ku Tokyo, Japan 105-0014 Tel: +81 3 5419 1990
17