 Feedback
|
Table Of Contents
Cisco Wide Area Application Services vWAAS Installation and Configuration Guide
Displaying Version Information
Obtaining Documentation and Submitting a Service Request
Cisco Wide Area Application Services vWAAS Installation and Configuration Guide
April 30, 2013Contents
This document describes how to install and configure virtual WAAS (vWAAS) on a VMware virtual machine (VM). The vWAAS software is a virtual form of WAN optimization that supports a virtual private cloud, and on- demand provisioning and teardown, reducing the branch office and data center footprint.
This document includes the following sections:
•
Displaying Version Information
•
Overview
The vWAAS software supports WAN optimization in a cloud environment where physical WAE devices cannot usually be deployed. It also follows the VMware ESXi standard as the preferred platform to deploy data center applications and services.
Virtualization provides various benefits like elasticity, ease of maintenance, and a reduction of branch office and data center footprint. Virtual WAN optimization is the solution to virtual private cloud deployments that require on-demand provisioning and teardown. (See Figure 1.)
Figure 1 vWAAS—Virtual Private Cloud
vWAAS can be deployed at the traditional WAN-edge, in both the branch office and data center. It can also be deployed close to the server when vPATH interception is used.
Requirements
This section includes the requirements for vWAAS:
•
–
—64-bit CPU hardware from the VMware compatibility list (HCL).
—Intel VT (virtualization technology) enabled in the BIOS.
–
•
–
–
Refer to the "Installing the Operating System or Hypervisor" chapter of the Getting Started guide for Cisco UCS E-Series Servers for download instructions
–
•
•
The following VMFS (Virtual Machine File System) limitations apply:
•
•
•
•
•
Note
Installing the vWAAS VM
You must first install the vWAAS VM on the VMware server using vSphere before configuring vWAAS. To install the vWAAS VM, follow these steps:
Step 1
Figure 2 vWAAS—Deploy OVF Template
The Source window appears.
Step 2
The Open window appears.
Step 3
Step 4
The Name and Location window appears.
Step 5
Figure 3 vWAAS—Name and Data Center Location
The Cluster window appears (if a cluster is configured), or the Resource Pool window appears (if a resource pool is configured). Otherwise, the Datastore window appears (in this case, skip to Step 7).
Step 6
The Datastore window appears.
Step 7
Figure 4 vWAAS—Datastore
Note
The Disk Format window appears.
Step 8
Figure 5 vWAAS—Disk Format
Note
The Network Mapping window appears.
Step 9
Figure 6 vWAAS—Network Mapping
The Ready to Complete window appears.
Step 10
The status window appears while the OVA file is being deployed. (See Figure 7.)
Figure 7 vWAAS—Status Window
Step 11
Figure 8 vWAAS—Completed
Click Close.
Step 12
Step 13
Figure 9 vWAAS—Console
For vWAAS configuration information, see the "Configuring vWAAS" section.
Configuring vWAAS
Once the vWAAS VM has been installed, you must configure the following vWAAS settings:
•
•
•
•
•
•
To configure vWAAS for network connectivity, follow these steps:
Step 1
The username is admin, and password is default.
Step 2
VWAAS(config)# interface virtual 1/0VWAAS(config-if)# ip address 2.1.6.111 255.255.255.0VWAAS(config-if)# exitStep 3
VWAAS(config)# ip default-gateway 2.1.6.1
Note
VWAAS(config)# ip primary-interface virtual 1/0
Note
Ping the IP addresses of the default gateway and Central Manager to verify they can be reached before continuing to the next step.
Step 4
VWAAS# license add EnterpriseStep 5
VWAAS(config)# central-manager address 2.75.16.100Step 6
VWAAS(config)# cms enable
Note
Step 7
Note
Refer to the Wide Area Application Services Configuration Guide to enable and configure WCCP interception.
Refer to the Wide Area Application Services Command Reference for more information on specific commands.
vPATH Interception
When vWAAS is deployed as a network service in the virtual data center, server traffic is intercepted in the Nexus 1000v virtual switch using vPATH interception and redirected to vWAAS for WAN optimization.
This section includes the following topics:
Overview
vPATH interception is configured on the port profile of the VM server in both directions to redirect the VM server packets to vWAAS. vWAAS receives the vPATH intercepted packet, performs WAN optimization, and returns the response packet to the VEM.
The vWAAS egress traffic received by the VEM is forwarded without further vPATH interception. (See Figure 10.)
Figure 10 vPATH Interception Overview
A special VLAN called the Nexus 1000v service VLAN is used for packets intercepted by vPATH and packets returned by vWAAS.
The Nexus 1000v switch uses the ARP mechanism in the service VLAN to check the status of vWAAS. If the switch does not receive any ARP replies from vWAAS during the timeout interval (18 to 24 seconds), the vWAAS is declared unreachable and it is removed from the service path. This behavior is known as fail-open mode, specified in the VN service configuration.
The key benefits of vPATH interception are the following:
•
•
•
•
•
Requirements
The following requirements apply to the Nexus 1000V to support vPATH interception:
•
•
•
•
•
•
Configuring vPATH
vPATH interception method is used in the Nexus 1000v switch for vWAAS deployment in the data center.
Note
Internet traffic destined to the server is intercepted by the Nexus 1000v virtual switch (residing in the ESX host) and redirected to vWAAS for WAN optimization. vWAAS can run either in the same ESX host or in another ESX host which is L2 adjacent.
Similarly, the traffic from the server is also intercepted by Nexus 1000v switch and redirected to vWAAS for WAN optimization. (See Figure 11.)
Figure 11 vWAAS—vPATH Interception
To configure vPATH interception in the Nexus 1000v for vWAAS, you must configure port and VN service profiles, in addition to enabling vPATH:
•
–
–
•
•
Refer to the Cisco Wide Area Application Services Command Reference for more information on the vn-service global configuration command.
Displaying Version Information
To display vWAAS version information, enter the following commands:
VWAAS# show versionCisco Wide Area Application Services Software (WAAS)Copyright (c) 1999-2012 by Cisco Systems, Inc.Cisco Wide Area Application Services (universal-k9) Software Release 5.1.1 (build b15Dec 17 2012)Version: oe294-5.1.1.15Compiled 02:35:03 Dec 17 2012 by masterDevice Id: 50:3d:e5:9c:8f:a5System was restarted on Mon Dec 17 19:32:34 2012.System restart reason: called via cli.The system has been up for 5 hours, 59 minutes, 45 seconds.VWAAS# show hardwareCisco Wide Area Application Services Software (WAAS)Copyright (c) 1999-2012 by Cisco Systems, Inc.Cisco Wide Area Application Services (universal-k9) Software Release 5.1.1 (build b15Dec 17 2012)Version: oe294-5.1.1.15Compiled 02:35:03 Dec 17 2012 by masterDevice Id: 50:3d:e5:9c:8f:a5System was restarted on Mon Dec 17 19:32:34 2012.System restart reason: called via cli.The system has been up for 6 hours, 40 seconds.CPU 0 is GenuineIntel Intel(R) Pentium(R) CPU G6950 @ 2.80GHz (rev 37)running at 2792MHz.CPU 1 is GenuineIntel Intel(R) Pentium(R) CPU G6950 @ 2.80GHz (rev 37)running at 2792MHz.Total 1 CPU, 2 CPU Cores, and 2 CPU Threads.4096 Mbytes of Physical memory.3968 MBytes of flash memory14 GigabitEthernet interfaces1 Console interface with RJ45 and mini-USB connectors1 external USB interfaceCavium Nitrox XL NPX (CN1620) Crypto Accelerator [ OK ]Quack Chip Echo Test: PASSWAVE-294-K9BIOS Information:Vendor :American Megatrends Inc.Version :A33C116ARel. Date :04/28/2011System Power Restore : Power OnMainboard info:Model : OE294Serial Number : FCH1524V01QDetailed Memory Device (DIMM) configurationSize Locator Position Serial Number2048 MB CHANNELA_DIMM1 CHANNELA 58048EDE2048 MB CHANNELB_DIMM1 CHANNELB 570489DEList of all disk drives:Physical disk information:disk00: Present 9XE005EF (h00 c00 i00 l00 - Int DAS-SATA)238472MB(232.9GB)Mounted file systems:MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%/swstore internal /dev/sda2 1983MB 944MB 1039MB 47%/state internal /dev/sda3 5951MB 489MB 5462MB 8%/local/local1 SYSFS /dev/sda6 11903MB 3477MB 8426MB 29%/sw internal /dev/sda1 1983MB 945MB 1038MB 47%/state/likewise/swinternal /dev/sda1 1983MB 945MB 1038MB 47%/state/likewise/local/local1internal /dev/sda6 11903MB 3477MB 8426MB 29%/local/local1/spoolPRINTSPOOL /dev/data1/spool 991MB 32MB 959MB 3%/obj1 CONTENT /dev/data1/obj 101177MB 139MB 101038MB 0%/dre1 CONTENT /dev/data1/dre 39677MB 39078MB 599MB 98%/ackq1 internal /dev/data1/ackq 1189MB 0MB 1189MB 0%/plz1 internal /dev/data1/plz 2379MB 1MB 2378MB 0%No RAID devices present.Disk encryption feature is disabled.Primary Power Supply Unit (Installed)PCI express link speed : 5.0 GT/s (Optimal)PCI express link width : Gen 2 (x8) (Optimal)Total number of system fans is 5Diskless Startup
Under rare conditions, the vWAAS VM may boot into diskless mode if other VMs on the host VM server do not release control of system resources or the physical disks become unresponsive. The vWAAS device raises a disk_failure critical alarm for disk01 and the show disk details EXEC command shows disk01 as Not used until replaced.
To recover from this failure, follow these steps:
Step 1
vwaas# configvwaas(config)# no disk disk-name disk00 shutdown forcevwaas(config)# exitStep 2
vwaas# reload
Related Documentation
For additional information on the Cisco WAAS software, see the following documentation:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2010-2013 Cisco Systems, Inc. All rights reserved.
