Cisco vWAAS Configuration Guide (for WAAS 6.4.3x)

TAR Archive Package for Cisco vWAAS on RHEL KVM in Cisco WAAS Version 5.x to 6.2.x

For Cisco vWAAS on RHEL KVM in Cisco WAAS Version 5.x through 6.2.x, Cisco provides a TAR archive or No Payload Encryption (NPE) TAR archive package for each Cisco vWAAS connection profile (examples shown in Table 6-3) and for each Cisco vCM connection profile (examples shown in Table 6-4).

Table 6-5 shows the files included for deploying Cisco vWAAS on RHEL KVM, and for deploying Cisco vWAAS with Cisco Network Functions Virtualization Infrastructure Software (Cisco NFVIS). For more information on Cisco NFVIS and Cisco Network Functions Virtualization (Cisco NFV), see the Cisco Enterprise Network Functions Virtualization Solution Overview. For more information on Cisco vWAAS with Cisco NFVIS, see the chapter “Cisco vWAAS with Cisco Enterprise NFVIS” .

Note For a listing of hypervisor OVA, zip, and tar.gz files for Cisco vWAAS, see the Cisco Wide Area Application Services (WAAS) Download Software page and select the Cisco WAAS software version used with your Cisco vWAAS instance.

Table 6-3 OVA Package Format Examples for Cisco vWAAS on RHEL KVM in Cisco WAAS Version 5.x to 6.2.x

Table 6-4 Cisco OVA Package Formats for Cisco vCM in Cisco WAAS Version 5.x to 6.2.x

Table 6-5 Installation Files for Cisco vWAAS on RHEL KVM and Cisco vWAAS with Cisco NFVIS in WAAS 5.x to 6.2.x

Installing Cisco vWAAS on RHEL KVM in Cisco WAAS Version 5.x to 6.2.x

This section contains the following topics:

• Using the Launch Script to Deploy Cisco vWAAS on RHEL KVM in WAAS Version 5.x to 6.2.x
• Using the EzDeploy Script to Deploy Cisco vWAAS on RHEL KVM on Cisco UCS-E in WAAS Version 5.x to 6.2.x

Using the Launch Script to Deploy Cisco vWAAS on RHEL KVM in WAAS Version 5.x to 6.2.x

To use the launch script (launch.sh) to deploy Cisco vWAAS on RHEL KVM, follow these steps:

Step 1 Launch the Cisco vWAAS VM. (You must have root permissions to launch the Cisco vWAAS VM.)

Step 2 Create a new directory to hold the extracted contents of tar.gz.

Step 3 Copy tar.gz into the specified directory.

Step 4 To extract the tar.gz gzip file, use this command:

tar -zxvf Cisco-KVM-vWAAS-ModelNumber-Version-BuildNumber.tar.gz

Example:

tar -zxvf Cisco-KVM-vWAAS-200-6.2.3d.b-68.tar.gz

The contents of the tar.gz file are:

• INSTRUCTIONS.TXT
• Disk-0.qcow
• Disk-1.qcow
• Disk-2.qcow
• vm_tap.xml
• vm_macvtap.xml
• launch.sh
• ezdeploy.sh
• ezdeploy.qstatus.exp

Step 5 To launch Cisco vWAAS, run the launch.sh script:

• To check the prerequisite conditions, use the /launch.sh check command.
• To launch Cisco vWAAS using the OVS bridge, use the./launch.sh vm-name bridge bridge1-name bridge2-name command.

– bridge1-name and bridge2-name: The OVS bridges already created in the host.

Note Before using the /launch.sh vm-name bridge bridge1-name bridge2-name command, verify that the OVS bridges are created and are in working state.

• To launch Cisco vWAAS using macvtap, use the /launch.sh vm-name macvtap interface1-name interface2-name command.

– vm-name: The specified name of the Cisco vWAAS VM.

– interface1-name and interface2-name: The specified Ethernet interfaces of the host machine.

The Cisco vWAAS is launched.

• (Optional) To view Cisco vWAAS, use the VM GUI or the virsh list command.
• (Optional) To connect to the console, use the VM GUI or the virsh console vm-name command.
• (Optional) To power down Cisco vWAAS, use the virsh destroy vm-name command.
• (Optional) To undefine Cisco vWAAS:

1. Use the virsh undefine vm-name command.

2. Remove the directory with the specified vm-name.

Note If you want to create another Cisco vWAAS of the same model, repeat this procedure. The specified directory, for example, Basic, will then have two VMs, Basic1 and Basic2. Disks for these VMs will be stored in the subdirectories Basic1 and Basic2, respectively.

Using the EzDeploy Script to Deploy Cisco vWAAS on RHEL KVM on Cisco UCS-E in WAAS Version 5.x to 6.2.x

Use the EzDeploy script for simplified deployment of a Cisco vWAAS. Note that the EzDeploy script is not used for the Cisco vCM.

The following are the prerequisites for launching the EzDeploy script:

• To launch the Cisco vWAAS VM, you must have root permission.
• The following software and utility packages must be installed before using the EzDeploy script:

– QEMU

– Libvirt

– Genisoimage

– Expect script (required only if you choose to run EzDeploy’s capability for auto-monitoring Cisco WAAS Central Manager registration status)

• Verify the following:

– There is sufficient disk and RAM memory to deploy another Cisco vWAAS.

– Compatibility of software versions.

– Availability and readiness of network connectivity.

Note Because EzDeploy leverages the launch.sh script to launch a Cisco vWAAS, the launch.sh script, as well as all the necessary files associated with it, must be present, intact, and not manually removed or manually moved elsewhere.

To use the EzDeploy script (ezdeploy.sh) to deploy Cisco vWAAS on RHEL KVM on Cisco UCS-E, follow these steps:

Step 1 Launch the Cisco vWAAS VM.

Step 2 Create a new directory to hold the extracted contents of tar.gz.

Step 3 Copy tar.gz into the specified directory.

Step 4 To extract the tar.gz gzip file, use the tar -zxvf Cisco-KVM-vWAAS-200-6.2.0.b-80.tar.gz command.

The contents of the tar.gz file are:

• INSTRUCTIONS.TXT
• Disk-0.qcow
• Disk-1.qcow
• Disk-2.qcow
• vm_tap.xml
• vm_macvtap.xml
• launch.sh
• ezdeploy.sh
• ezdeploy.qstatus.exp

Step 5 Run the ezdeploy.sh script:

a. During execution of the ezdeploy.sh, you are prompted for bootstrap configuration parameters:

– vWAAS KVM name: The name is dependent on whether or not you provide the Cisco vWAAS’ bootstrap configuration.

If you have not provided the Cisco vWAAS’ bootstrap configuration: the name is set as the name of the guest KVM to be created. not the Cisco vWAAS’ host name.

If you have provided the vWAAS’ bootstrap configuration: the Cisco vWAAS’ host name is set and used in both instances.

– Cisco vWAAS local IP address and mask

– Default GW IP address: An address on the ISR-4000 series RP that is reachable by the Cisco vWAAS and has external network connectivity

– IP address of the Cisco WAAS Central Manager with which the Cisco vWAAS will register

– One NTP server address, without authentication. If you want to have authentication or multiple NTP servers, use the Cisco WAAS Central Manager to configure these after the Cisco vWAAS is powered up.

– (Optional) DNS server address

The ezdeploy.sh script performs a validation before accepting each parameter.

b. After input collection is completed, the following information is saved:

– The bootstrap configuration is saved in the bootstrap-cfg.xml file in the directory created for this KVM.

– The execution log and error log of the script are saved in the ezdeploy-log.txt file in the directory created for this KVM.

– For the Cisco vWAAS in this KVM, the error log is saved in errorlog/ezdeploy-errorlog.txt.

Note By default, all configuration and error logs saved in the specified KVM directory are not deleted, even if they have recorded errors. Therefore, you should allow for debugging. If you do not want to generate log files, you must confirm this choice at the end of the script execution, after input entry.

c. After the EzDeploy script is run, the Cisco vWAAS is fully up and running. Registration with the specified Cisco WAAS Central Manager and the NTP server are automatically started after installation of their corresponding CLIs.

• Optional: To view Cisco vWAAS, use the VM GUI or the virsh list command.
• Optional: To connect to the console, use the VM GUI or the virsh console vm-name command.
• Optional: To power down Cisco vWAAS, use the virsh destroy vm-name command.
• Optional: To undefine Cisco vWAAS:

1. Use the virsh undefine vm-name command.

2. Remove the directory with the specified vm-name.

Unified OVA Package for Cisco vWAAS on KVM in WAAS Version 6.4.1 and Later

For Cisco vWAAS on RHEL KVM in Cisco WAAS Version 6.4.x and later, Cisco provides a single, unified OVA or NPE OVA package for each hypervisor type, which can be used with all Cisco vWAAS models for that hypervisor.

Each unified OVA package file is a preconfigured VM image that is ready to run on a particular hypervisor. The launch script for each unified OVA package provides the model and other required parameters to launch vWAAS with WAAS in the required configuration.

The following are examples of the unified OVA and NPE OVA package filenames for vWAAS on RHEL KVM:

• OVA: Cisco-KVM-vWAAS-Unified-6.4.3c-b-42.tar
• NPE OVA: Cisco-KVM-vWAAS-Unified-6.4.3c-b-42-npe.tar

The unified OVA package for vWAAS on RHEL KVM and KVM on CentOS contains the following files:

• Flash disk image
• Data system disk
• Akamai disk
• INSTRUCTIONS.TXT: Describes the procedure for deploying the virtual instance and using the launch.sh file.
• package.mf template file and bootstrap-cfg.xml: These two files work together on the Cisco NFVIS platform with the image_properties.xml file as Day-0 configuration template.
• ezdeploy.sh: The script used to deploy vWAAS on UCS-E.
• exdeploy_qstatus.exp: The dependent file for the ezdeploy.sh script image_properties.xml. A VM configuration template file used on the Cisco NFVIS platform.
• launch.sh: The launch script to deploy Cisco vWAAS on Linux KVM.
• vm_macvtap.xml: Configuration file for vWAAS deployment using host machine interfaces with the help of the macvtap driver.
• vm_tap.xml: Configuration file for vWAAS deployment using virtual bridge or Open Virtual Switch (OVS) present in the host machine.

Installing Cisco vWAAS on KVM in Cisco WAAS Version 6.4.1 and Later

This section contains the following topics:

• Using the Launch Script to Deploy Cisco vWAAS on RHEL KVM on CentOS in Cisco WAAS Version 6.4.1 and Later
• Using the EzDeploy Script to Deploy Cisco vWAAS on RHEL KVM on CentOS in Cisco WAAS Version 6.4.1 and Later

Note For how to install Cisco vWAAS with Cisco NFVIS on the Cisco ENCS 5400-W Series, see the Cisco vWAAS Bundled Image Upgrade for ENCS 5400 Series, with RMA Process for Cisco EOS/EOL WAVE Devices.

Using the Launch Script to Deploy Cisco vWAAS on RHEL KVM on CentOS in Cisco WAAS Version 6.4.1 and Later

To use the launch script (launch.sh) to deploy Cisco vWAAS or vCM on RHEL KVM on CentOS, follow these steps:

Step 1 At [root@localhost hostname] enter the following:

The Model Menu is displayed:

Step 2 Enter the number of the Cisco vWAAS or Cisco vCM model for your system.

After you select the Cisco vWAAS or Cisco vCM model type, the launch script completes the RHEL CentOS KVM deployment.

Using the EzDeploy Script to Deploy Cisco vWAAS on RHEL KVM on CentOS in Cisco WAAS Version 6.4.1 and Later

To use the EzDeploy script (ezdeploy.sh) to deploy Cisco vWAAS or vCM on RHEL KVM on CentOS, for Cisco vWAAS models up to 6,000 connections, follow these steps:

Step 1 At [root@localhost ezdeploy] enter the following:

Step 2 The Model Menu is displayed:

Step 3 Enter the number of the Cisco vWAAS model type for your system.

After you select the Cisco vWAAS model type, the EzDeploy script completes the RHEL KVM/KVM on CentOS deployment.

Using the Unified OVA Package to Deploy Cisco vWAAS with Cisco NFVIS

To use the unified OVA package to deploy Cisco vWAAS on RHEL KVM on CentOS with Cisco NFVIS, follow these steps:

Step 1 In the Navigation pane of the Cisco Enterprise NFVIS portal, choose VM Life Cycle > Deploy.

The registered VM images are displayed in the VM Deployment window.

Step 2 Select the Cisco vWAAS as the VM.

Step 3 Drag and drop the Cisco vWAAS in the Network Topology area.

After you select Cisco vWAAS as the VM, the Cisco vWAAS attributes and attribute choices are displayed in the VM Details pane.

Step 4 Enter the following information in the VM Details pane:

a. In the VM Name field, edit the Cisco vWAAS name for your system.

b. At the Image drop-down list, choose the unified OVA package for the Cisco vWAAS.

c. At the Profile drop-down list, choose the Cisco vWAAS connection profile for your system.

d. Other fields are automatically filled in by the system.

Step 5 Connect the Cisco vWAAS to a specified network by dragging the pointed arrow from the Cisco vWAAS to the specified network.

Note During this process, the VM Details pane displays the Virtual Network Interface Card (vNIC) details: VM name, network name, and vNIC ID. The vNIC ID number is automatically generated; you can change this number, if needed, by using the vNIC ID drop-down list.

Step 6 Click Deploy.

The window is refreshed to display the deployment status.

Interoperability Guidelines for Cisco vWAAS on KVM and KVM on CentOS

Consider the following interoperability guidelines for Cisco vWAAS on KVM:

Interoperability guidelines for Cisco WAAS versions and Cisco vWAAS on KVM:

• Cisco vWAAS on RHEL KVM is available for vWAAS in WAAS Version 6.2.1 and later.
• Cisco vWAAS on KVM on CentOS is available for vWAAS on WAAS Version 6.2.3x and later.

Interoperability guidelines for OVS and vWAAS on KVM:

• The Cisco Discovery Protocol (CDP) is not supported for Open Virtual Switch (OVS) on RHEL KVM on CentOS, therefore the show cdp command cannot be used for Cisco vWAAS on RHEL KVM on CentOS.
• For Cisco vWAAS in WAAS Version 6.2.3x and later, there is inline Cisco vWAAS support for the OVS switch, with additional settings in Cisco vWAAS.

To configure inline Cisco vWAAS support for the OVS switch:

1. Install CentOS 7.2 on UCS-C240.

2. Configure OVS switch on the KVM host.

3. Deploy the KVM vWAAS OVAs with the OVS switch on KVM host.

4. Power off the Cisco vWAAS.

5. Add two additional interfaces.

6. Using the virt-manager, map the bridge ID in Cisco vWAAS:
[root@localhost kvm]# virsh edit vwaas-name

The domain vWAAS XML configuration is changed.

7. Using the virt-manager, edit the virtual type:
virtualport type=’openvswitch’/

8. Example:

<interface type='bridge'>

<mac address='52:54:00:ea:3f:7b'/>

<source bridge='br2'/>

<virtualport type='openvswitch'/>

<model type='virtio'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>

</interface>

<interface type='bridge'>

<mac address='52:54:00:7f:7c:99'/>

<source bridge='br3'/>

<virtualport type='openvswitch'/>

<model type='virtio'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>

</interface>

Traffic Interception Methods for Cisco vWAAS on RHEL KVM

For traffic interception for Cisco vWAAS on RHEL KVM, you can use WCCP (WCCP GRE or WCCP L2) or Cisco AppNav.

Note When you use any of the traffic interception methods for Cisco vWAAS on RHEL KVM, you must disable Generic Receive Offload (GRO) on the Cisco UCS NIC. Use the ethtool -K nic_interface_name gro off command on the KVM host to disable GRO, for example: ethtool -K enp3sof2 gro off. If you do not disable GRO, traffic is not recognized, and packets are discarded.

If you upgrade the Cisco UCS NIC firmware to the latest version, you do not have to disable the GRO parameter.

For more information on configuring traffic interception methods, see the Cisco Wide Area Application Services Configuration Guide.