Configuring Cisco vWAAS and Viewing vWAAS Components

This chapter describes how to configure Cisco vWAAS settings, such as Cisco WAAS Central Manager address and traffic interception settings, and how to identify a Cisco vWAAS on the Cisco WAAS Central Manager or through the Cisco WAAS CLI.

This chapter contains the following sections:

Configuring Cisco vWAAS Settings

Before you begin

After the Cisco vWAAS VM has been installed, you must configure the following Cisco vWAAS settings:

  • IP address and netmask

  • Default gateway

  • Cisco WAAS Central Manager address

  • Settings for corresponding VLAN in the VM for network reachability

  • Centralized Management System (CMS)

  • Traffic interception (see Configuring Cisco vWAAS Traffic Interception)

Procedure

Step 1

In the VMware vSphere Client, click the Console tab and log in to the Cisco vWAAS console, using the username admin and the password default.

Step 2

Configure the IP address and netmask using the interface virtual command, as shown in the following example:

Example:


VWAAS(config)# interface virtual 1/0
VWAAS(config-if)# ip address 2.1.6.111 255.255.255.0
VWAAS(config-if)# exit
Note 
For Cisco vWAAS in WAAS Version 6.1.x and later, the Cisco vWAAS and Cisco vCM devices require both the virtual (network) interfaces to be “present”. One or both the virtual interfaces should be active for the Cisco vWAAS and Cisco vCM devices to be operational after power up.
Step 3

Configure the default gateway using the ip command: 

VWAAS(config)# ip default-gateway 2.1.6.1

Ping the IP addresses of the default gateway and Central Manager to verify if they can be reached, before continuing to the next step.

Step 4

Add the Central Manager address using the central-manager command:

Example:


VWAAS(config)# central-manager address 2.75.16.100
Step 5

Enable CMS to register with the Central Manager using the cms command:

Example:


VWAAS(config)# cms enable
Note 
Cisco vWAAS registration with the Central Manager is mandatory before traffic can be optimized. To ensure that Cisco vWAAS registration with the Cisco WAAS Central Manager is successful, confirm that this configured interface for the Cisco WAAS Central Manager is the primary Cisco WAAS Central Manager interface.
Step 6

Configure traffic interception: WCCP, AppNav, or L2 Inline. For more information on traffic interception methods for Cisco vWAAS, see Configuring Cisco vWAAS Traffic Interception.

Configuring Cisco vWAAS Traffic Interception

You can configure the following traffic interception methods for Cisco vWAAS.

  • WCCP: Available for Cisco vWAAS in all Cisco WAAS versions.

  • AppNav: Available for Cisco vWAAS in all Cisco WAAS versions

  • L2 Inline: Available for Cisco WAAS Version 6.2.x and later, for Cisco vWAAS with RHEL KVM. The following table shows the commands for configuring and displaying information on L2 Inline interception for Cisco vWAAS.

The following table provides descriptions of each traffic interception method.

Table 1. Traffic Interception Methods for Cisco vWAAS

Traffic Interception Method

Description

WCCP

Specifies interactions between one or more routers (or L3 switches) and one or more application appliances, web caches, and caches of other application protocols, to establish and maintain the transparent redirection of selected types of traffic. The selected traffic is redirected to a group of appliances. Any type of TCP traffic can be redirected.

WCCP uses a WCCP-enabled router or L3 switch.

Note 
You can configure WCCP-GRE or L2 Inline as the redirection method for Cisco vWAAS running on a Cisco UCS-E inside a Cisco ISR G2, where the Cisco UCS-E interface is configured as IP unnumbered in Cisco IOS.

For more information, see the chapter "Configuring Traffic Interception" in the Cisco Wide Area Application Services Configuration Guide.

AppNav

A policy and class-based traffic interception method that reduces dependency on the intercepting switch or router by distributing traffic among WAAS devices for optimization.

For more information, see the chapter "Configuring Cisco AppNav" in the Cisco Wide Area Application Services Configuration Guide.

L2 Inline

Places the Cisco vWAAS in the data path between WAN and LAN, with an interface facing each segment to inspect and optimize the traffic, as needed. For L2 Inline, traffic is forwarded directly without being sent back to the router.

The Cisco vWAAS interfaces, with virtual NICs, appear as virtual interfaces in the Cisco WAAS Central Manager for the running configuration. By default, the NICs supporting Inline mode do not appear in the running configuration when L2 Inline interception is not enabled.

Note 
Cisco vWAAS in Cisco WAAS Version 6.2.1 does not include fail-to-wire capability.

For more information, see the chapter "Configuring Traffic Interceptions" in the Cisco Wide Area Application Services Configuration Guide.

The following table shows the commands for configuring and displaying information on L2 Inline interception for Cisco vWAAS.

Table 2. CLI Commands for L2 Inline Traffic Interception

Mode

Command

Description

Global Configuration

(config) interception-method inline

Enables L2 inline traffic interception on Cisco vWAAS.

Interface Configuration

(config-if) cdp

Enables CDP (Cisco Discovery Protocol) on the interface on a Cisco WAAS device. (To globally enable the CDP interval and holdtime options, run the cdp global configuration command.)

(config-if) description

Configures the description for a network interface.

(config-if) encapsulation

Sets the encapsulation type for the interface.

(config-if) exit

Terminates interface configuration mode and returns you to global configuration mode.

(config-if) inline

Enables inline traffic interception for an inlineGroup interface.

For more information on the inline interface configuration command, including specifying an inline group and inline interception for VLAN IDs, see the Cisco Wide Area Application Services Command Reference.

(config-if) ip

Configures the IPv4 address or subnet mask on the interface of a Cisco WAAS device, or negotiates an IP address from DHCP on the interface of a Cisco WAAS device.

(config-if) ipv6

Configures the IPv6 address on the interface of a Cisco WAAS device, or negotiates an IP address from DHCP on the interface of a Cisco WAAS device.

(config-if) load-interval

Configures the interval at which to poll the network interface for statistics.

(config-if) shutdown

Shuts down a specific hardware interface on a Cisco WAAS device, and shuts down the inlinegroup interface to bypass the traffic, and does not optimize the traffic.

EXEC

show interception-method

Displays the configured traffic interception method.

show interface InlineGroup

Displays inline group information and the slot and inline group number for the selected interface.

show interface inlineport

Displays the inline port information and the slot and inline group number for the selected interface.

show running-config

Display the current running configuration.

For more information on these commands, see the Cisco Wide Area Application Services Command Reference.

Identifying a Cisco vWAAS Device

This section describes how to:

  • Identify a Cisco vWAAS model.

  • Identify a Cisco vWAAS device on the Cisco WAAS Central Manager.

  • Identify a Cisco vWAAS device with the Cisco CLI.

To identify a Cisco vWAAS model:

As shown in the following table, a Cisco vWAAS model is determined by the number of vCPUs and the maximum number of TCP connections.

Table 3. Cisco vWAAS Models with vCPUs and Maximum TCP Connections

Cisco vWAAS Model

Number of vCPUs

Maximum Number of TCP Connections

vWAAS-150

1

200

vWAAS-200

1

200

vWAAS-750

2

750

vWAAS-1300

2

1,300

vWAAS-2500

4

2,500

vWAAS-6000

4

6,000

vWAAS-6000-R

(earliest supported version: Cisco WAAS Version 6.4.x)

4

6,000

vWAAS-12000

4

12,000

vWAAS-50000

8

50,000

Identifying a Cisco vWAAS device on the Cisco WAAS Central Manager:

There are two windows on the Cisco WAAS Central Manager that show identifying information for a Cisco vWAAS device.

  • Choose Devices > device-name. On the dashboard for the device, in the Device Info > Hardware Details section, the Model column shows the vWAAS device type.

  • Choose Device > All Devices, which shows a listing of all the devices, including Device Type.

The following table shows the displayed Cisco vWAAS device types.

Table 4. Cisco vWAAS Device Types Displayed in Cisco WAAS Central Manager

vWAAS Device

vWAAS Device Type shown in Cisco WAAS Central Manager

vWAAS on Cisco ISR-WAAS

OE-VWAAS-KVM

vWAAS on Cisco NFVIS

OE-VWAAS-KVM

vWAAS on VMware ESXi

OE-VWAAS-ESX

vWAAS on Microsoft Hyper-V

OE-VWAAS-HYPERV

vWAAS on RHEL KVM

OE-VWAAS-KVM

vWAAS on KVM on CentOS

OE-VWAAS-KVM

vWAAS on SUSE Linux

OE-VWAAS-GEN-LINUX

vWAAS in Microsoft Azure

OE-VWAAS-AZURE

vWAAS in OpenStack

OE-VWAAS-OPENSTACK

Identifying a Cisco vWAAS Device with the Cisco WAAS CLI:

The following table shows the commands used to display Cisco vWAAS device information. For more information on these commands, see the Cisco Wide Area Application Services Command Reference.

Table 5. CLI Commands for Cisco vWAAS Device Information

Mode

Command

Description

user-level EXEC and privileged-level EXEC

show version

Displays version information about the Cisco WAAS software currently running on the Cisco vWAAS device, including date and time system last started, and the length of time the system has been running since the last reboot.

  • (Optional) Run the show version last command to display version information for the last saved image.

  • (Optional) Run the show version pending command to display version information for the pending upgraded image.

privileged-level EXEC

show hardware

Displays system hardware status for the Cisco vWAAS device, including:

  • Startup date and time, the run time since startup, microprocessor type and speed, and a list of disk drives.

privileged-level EXEC

show tfo detail

Displays Transport Flow Optimization (TFO) information, including:

  • State: Registered or Not Registered

  • Default Action: Drop or Use

  • Connection Limit: The maximum TFO connections handled before new connection requests are rejected.

  • Effective Limit: The dynamic limit relating to how many connections are handled before new connection requests are rejected.

  • Keepalive Timeout: The connection keepalive timeout, in seconds.

Cisco vWAAS System Partitions

For all Cisco vWAAS models, the system partition size for /sw and /swstore is increased from 1 GB to 2GB, under the following conditions:

  • The disk delete-preserve-software command deletes all the disk partitions and preserves the current software version.

  • The partition size of 2 GB each for /sw and /swstore is effective only after a new OVA/ISO installation.

  • During an upgrade, the newly defined partition size becomes effective only after you run the disk delete-partitions diskname command.


Caution

During a downgrade, the partition size of /sw and /swstore each remains at 2GB, which leads to a file system size mismatch.

For more information on Object Cache data partitions and Akamai Cache data partitions, see the chapter "Maintaining Your Cisco WAAS System" in the Cisco Wide Area Application Services Configuration Guide.

Operating Guidelines for Cisco vWAAS and Cisco WAAS

Consider the following guidelines when using Cisco vWAAS in Cisco WAAS:

  • For Cisco vWAAS in WAAS Version 6.1.x and later, the Cisco vWAAS and Cisco vCM devices require both virtual (network) interfaces to be present, but both need not be active. If only one virtual interface is active, the Cisco vWAAS and Cisco vCM devices will not be operational after power up. For more information, see Configuring Cisco vWAAS Settings.

  • If the virtual host was created using an OVA file of Cisco vWAAS in Cisco WAAS Version 5.0 or earlier, and you have upgraded Cisco vWAAS in Cisco WAAS, you must verify that the SCSI Controller Type is set to VMware Paravirtual. Otherwise, Cisco vWAAS will boot with no disk available and will fail to load the specified configuration.

    If needed, change the SCSI Controller Type to VMware Paravirtual by following these steps:

    1. Power down the Cisco vWAAS.

    2. From the VMware vCenter, choose vSphere Client > Edit Settings > Hardware.

    3. Choose SCSI controller 0.

    4. From the Change Type drop-down list, verify that the SCSI Controller Type is set to VMware Paravirtual. If this is not the case, choose VMware Paravirtual.

    5. Click OK.

    6. Power up the Cisco vWAAS, in Cisco WAAS Version 6.1.x or later.

Cisco vWAAS with Single Root I/O Virtualization

This section contains the following topics:

About SR-IOV

Single-Root I/O Virtualization (SR-IOV) is a standard developed by the Peripheral Component Interconnect Special Interest Group (PCI-SIG) to improve virtualization of PCI devices.

SR-IOV enables the VMs to share the I/O device in a virtualized environment. SR-IOV achieves this by bypassing the hypervisor’s involvement in data movement:

  • SR-IOV provides independent memory space, interrupts, and Cisco Data Migration Assistant (DMA) streams for each VM.

  • The SR-IOV architecture allows a device to support multiple virtual functions, and therefore, minimizes the hardware cost of each additional function.

  • SR-IOV-enabled Ethernet controllers support direct assignment of part of the port resources to guest operating systems that use the SR-IOV standard. This capability enhances the performance of the guest VMs.

The following table shows the two types of functions used with SR-IOV.

Table 6. SR-IOV Physical Functions and Virtual Functions

Function

Description

Physical Functions

  • A full PCI Express (PCIe) function that includes the SR-IOV extended capability, which is used to configure and manage the SR-IOV functionality.

  • Physical functions are discovered, managed, and configured as normal PCIe devices. Physical functions configure and manage the SR-IOV functionality by assigning virtual functions.

Virtual Functions

  • A lightweight PCIe function that contains all the resources necessary for data movement, but has a carefully minimized set of configuration resources.

  • Each Virtual Function is derived from a Physical Function. The number of Virtual Functions an Ethernet controller can have is limited according to the device hardware.

Interoperability and Platforms Supported for Cisco vWAAS with SR-IOV

This section describes the following topics:

  • Cisco WAAS Central Manager and Cisco vWAAS with SR-IOV

  • Platforms supported for Cisco vWAAS with SR-IOV

Cisco WAAS Central Manager and Cisco vWAAS with SR-IOV:

  • Devices with SR-IOV are registered with the Cisco WAAS Central Manager in the same manner as other Cisco vWAAS devices. Run the cms deregister EXEC command to deregister these devices as you would for other Cisco vWAAS devices.

  • The following list shows how vWAAS devices with SR-IOV are displayed on the Cisco WAAS Central Manager:

    • Cisco vWAAS with SR-IOV on VMware ESXi is displayed as OE-VWAAS-ESX.

    • Cisco vWAAS with SR-IOV on KVM (RHEL, CentOS or Cisco NFVIS) is displayed as OE-VWAAS-KVM.

Platforms supported for Cisco vWAAS with SR-IOV:

Consider the following operating considerations for platforms supported for Cisco vWAAS with SR-IOV:

  • Although Intel X710 is capable of 10 Gbps speed, vWAAS with SR-IOV using Intel X710 on NFVIS is supported for 1 Gbps speed, as part of vBranch solution.

  • The supported firmware version for Intel X710 NIC is 5.05

The following table shows the Cisco WAAS version and platforms supported for Cisco vWAAS with SR-IOV.

Table 7. Cisco WAAS Version and Platforms Supported for Cisco vWAAS with SR-IOV

Ethernet Controller

Hypervisor

Earliest Cisco WAAS Version Supported

Supported Cisco vWAAS Models

Intel I350

CentOS

6.4.1

  • vWAAS-150

  • vWAAS-200

  • vWAAS-750

  • vWAAS-1300

  • vWAAS-2500

  • vWAAS-6000

Intel X710

NFVIS

6.4.1

  • vWAAS-150

  • vWAAS-200

  • vWAAS-750

  • vWAAS-1300

  • vWAAS-2500

  • vWAAS-6000

CentOS

6.4.3

  • vWAAS-12000

  • vWAAS-50000

ESXi

6.4.3

  • vWAAS-12000

  • vWAAS-50000

  • vWAAS-150000

Upgrade and Downgrade Guidelines for Cisco vWAAS with SR-IOV

Consider the following when you upgrade or downgrade a Cisco vWAAS with SR-IOV:

  • Upgrade Guidelines

    • The upgrade procedure for Cisco vWAAS with SR-IOV is the same as for other vWAAS devices.

  • Downgrade Guidelines

    • Before a downgrade from Cisco vWAAS in Cisco WAAS Version 6.4.1x or 6.4.3 to an earlier version, from the host, remove those SR-IOV interfaces that do not support this functionality when operating in a Cisco WAAS version earlier than WAAS Version 6.4.1x. Downgrade of Cisco vWAAS instances with SR-IOV is blocked for unsupported WAAS versions.

    • At the device level, if you downgrade a Cisco vWAAS instance with SR-IOV to a version earlier than 6.4.1x or 6.4.3 (depending on your Cisco WAAS configuration), a warning message is displayed at the start of the downgrade process. This warning message is displayed if the device supports SR-IOV functionality, even if the device does not use the SR-IOV interface, because downgrade of vWAAS instances with SR-IOV is blocked for unsupported Cisco WAAS versions.

    • At the device group level, if you downgrade a device group that contains at least one device that supports SR-IOV functionality, a warning message is displayed at the start of the downgrade process, because downgrade of Cisco vWAAS instances with SR-IOV is blocked for unsupported Cisco WAAS versions.

For more information on the upgrade or downgrade process, see Release Notes for Cisco Wide Area Application Services.

Deploying Cisco vWAAS with SR-IOV

This section contains the following topics:

Deploying Cisco vWAAS with SR-IOV on VMware ESXi

This section contains the following topics:

Configuring Host Settings for Cisco vWAAS with SR-IOV on VMware ESXi for Cisco UCS C-Series
Before you begin

Before you begin, note the VMware ESXi host requirements for Cisco vWAAS with SR-IOV on Cisco UCS C-Series:

Table 8. VMware ESXi Requirements for Cisco vWAAS with SR-IOV on Cisco UCS C-Series

Intel X710 NIC Specification

Specification Value

Driver Name

i40e

Tested Driver Version

2.0.7

Tested Firmware Version

5.0.5

Note

Without compatible drivers, the Intel X710 will not be detected.
Procedure
Step 1

Log in to the VMware ESXi shell.

Step 2

Run the lspci | grep -i intel | grep -i 'ethernet\|network' command, and note the port order of this command.

Step 3

Run this command to create virtual functions:

# esxcli system module parameters set -m i40e -p max_vfs=Y,Z

Y,Z represents the number of VF's to be created respectively for each port.

Example 1: 

max_vfs=5,0 represents 5 VFs on adapter 1 port 1

Example 2: 

max_vfs=0,5 represents 5 VFs on adapter 1 port 2
[root@localhost:~]
[root@localhost:~] lspci | grep -1 intel | grep -1 'ethernet\|network'
0000:01:00.0 Network controller: Intel Corporation I350 Gigabit Network Connection (vmnic2)
0000:01:00.1 Network controller: Intel Corporation I350 Gigabit Network Connection (vmnic3)
0000:06:00.0 Network controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (vmnic0)
0000:06:00.1 Network controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (vmnic1)
0000:81:00.0 Network controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+(vmnic4)
0000:81:00.1 Network controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+(vmnic5)
[root@localhost:~]
[root@localhost:~] esxcli system module parameters set -m i40e -p max_vfs=5,0
[root@localhost:~]
Step 4

To verify the value of the VFs to be created, run the esxcli system module parameters list -m i40e command:

Step 5

To create the virtual functions, reboot the host.
Step 6

After the reboot is complete, verify the virtual functions by using either of the following options:

  • Run the VMware ESXi lspci command

  • Choose Host > Configuration > Hardware > Advanced Settings to display the VMware vSphere Client DirectPath I/O Configuration window.

Figure 1. VMware vSphere Client DirectPath I/O Configuration Window
Configuring SR-IOV Interfaces for Cisco vWAAS on VMware ESXi on Cisco UCS-C Series
Procedure
Step 1

After deploying the Cisco vWAAS, power down the Cisco vWAAS.

Step 2

Power up the vWAAS.
Step 3

Right-click and choose Edit Settings.

Step 4

Click the Virtual Machine Properties > Resources tab.

Step 5

At the Settings listing, choose Memory.

The Resource Allocation window is displayed.

Figure 2. Cisco vWAAS Resource Allocation Window
Step 6

Click Reserve all guest memory.

Step 7

Click OK.

Step 8

Click the Virtual Machine Properties > Hardware tab.

Step 9

Click Add.

The Device Type window is displayed.

Figure 3. Cisco vWAAS Add Hardware > Device Type Window
Step 10

For device type, select PCI Device.

Step 11

Click Next.

The Choose PCI Device window is displayed.

Figure 4. Cisco vWAAS Add Hardware > Choose PCI Device Window
Step 12

From the Specify the physical PCI/PCI3 Device to connect to: drop-down list, choose the virtual function you want to connect to.

Step 13

Click Next.

Step 14

Click Finish.

Step 15

To begin using the virtual function, start the VM.

Deploying Cisco vWAAS with SR-IOV on KVM

This section contains the following topics:

Configuring Host Settings for Cisco vWAAS on KVM or CentOS with SR-IOV on the Cisco UCS C-Series
Before you begin

One-time host settings are required to use the SR-IOV functionality on RHEL KVM or CentOS on the Cisco UCS C-Series.

Procedure
Step 1

Enable Intel Virtualization Technology for Directed I/O (VT-d) in the host BIOS.

To enable VT-d:

  • Use the cat /proc/cpuinfo | grep -E ‘vmx|svm’ | wc -l command to verify that you have enabled VT-d.

  • The command value should be greater than 0.

Step 2

Enable I/O MMU:

  1. In the /etc/default/grub file, add intel_iommu=on to GRUB_CMDLINE_LINUX.

  2. After you make changes to GRUB_CMDLINE_LINUX, the following message is displayed: 

    GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb
quiet intel_iommu=on"

  3. For the changes to take effect, compile by running grub2-mkconfig -o /boot/grub2/grub.cfg.

  4. Reboot the host.
Step 3

Enable the SR-IOV virtual functions.

  1. Verify the maximum number of virtual functions allowed for the specified interface.

    For example, if the SR-IOV-supported interface is enpls0f0, verify the value of /sys/class/net/enp1s0f0/device/sriov_totalvfs.

  2. Set the required number of virtual functions in /sys/class/net/enp1s0f0/device/sriov_numvfs.

    On the enpls0f0 interface, enter the following: 

    echo 7 > /sys/class/net/enp1s0f0/device/sriov_numvfs
Step 4

To remove the SR-IOV configuration for a specific interface, for example, enp1s0f0, run the command echo 0 at /sys/class/net/enp1s0f0/device/sriov_numvfs command and remove the lines with the enp1s0f0 interface name present in /etc/rc.d/rc.local.

Deploying Cisco vWAAS with SR-IOV on RHEL KVM or CentOS Using Deployment Script for Cisco UCS C-Series
Before you begin

Cisco vWAAS on RHEL KVM or CentOS for SR-IOV is deployed using the launch.sh script file on the Cisco UCS C-Series.

Procedure
Step 1

To check the prerequisite host configuration, run the following command:

./launch.sh check
Step 2

To launch the VM with bridge or macvtap interfaces, run the following command:

./launch.sh <vm_name> <intf_type> <intf1_name> <intf2_name>

  • The intf_type can be either bridge or macvtap.

  • The intf1_name and intf2_name are the desired names based on the selected intf_type.

Step 3

To launch Cisco vWAAS (not Cisco vCM) with SRIOV interface(s), run the following command:

./launch.sh <vm_name> <intf_type> <intf1_name> <inft_type> <intf2_name>

  • The first intf_type option can be bridge or macvtap or sriov.

  • The second intf_type option should be sriov.

  • The intf1_name and intf2_name are the desired names based on the selected intf_type.

Deploying Cisco vWAAS with SR-IOV on RHEL KVM or CentOS Using Cisco NFVIS Portal for Cisco ENCS 5400-W Series
Procedure
Step 1

From the Cisco Enterprise NFV Solution window, click the VM Deployment tab.

The VM Deployment window displays a navigation row, shown below, to highlight where you are in the VM deployment process.

VM Deployment Process Navigation Flow:

1 Images > 2 Profiles > 3 Networks > 4 Configuration > 5 Review & Deploy

Consider the following guidelines for VM deployment:

  • Before you enter information to begin the VM deployment process, the VM Deployment navigation row displays the element 1 Images as being highlighted.

  • You must specify all the parameters for the Cisco vWAAS VM during VM deployment. After the Cisco vWAAS VM is deployed, you cannot make changes to the Cisco vWAAS VM.

    To change any parameter for a deployed Cisco vWAAS VM, you must delete that Cisco vWAAS VM and deploy a new Cisco vWAAS VM.
Step 2

To register the Cisco vWAAS VM image: At the VN Name field, enter the name of the Cisco vWAAS VM.

Step 3

From the List of Images on the Device table listing, select an image for the Cisco vWAAS VM that will be deployed, or click Upload to upload an image.

The VM Deployment navigation row shows 2 Profiles as being highlighted.

Step 4

Click Next.

The Profiles window is displayed, showing the Select Profiles table listing, which has columns for profile name, CPUs, memory (in MB), and disk size (in MB).

Step 5

From the Select Profiles table listing, click the radio button next to the profile you want to use, or click "+" to add a new profile.

A new, empty row is displayed for you to enter information.
Step 6

To create the new profile, click Save.

Step 7

Click Next.

The VM Deployment navigation row shows 3 Networks as being highlighted.

The Select Network Interface window is displayed, showing the Select Network Interface table listing, which has columns for VNIC number and network name.

Step 8

From the Select Network Interface table listing:

  • Check the check box next to one or more NVIC numbers that you want to attached to the VM you selected or created in Steps 1 to Step 4, or

  • Click "+" to add a new VNIC for the specified VM.

    If you click "+" to create a new VNIC, a new empty row is displayed for you to enter information.
Step 9

To create the new VNIC, click Save.

The VM Deployment navigation row still shows 3 Networks as being highlighted.

The Networks and Bridges table listing is displayed, which you use to add or delete networks and associated bridges.

Consider the following as you use the Networks and Bridges table listing:

  • The table listing displays columns for network name, VLAN (if applicable), bridge, and port (if applicable).

  • The table listing shows the available networks and bridges on the NFVIS server. Initially, the table listing shows the default networks: lan-net and wan-net and associated bridges.

  • The top right corner of the table toolbar shows the selected row and the total number of rows, for example, Selected 2 / Total 4.

  • To associate multiple VLANs with a network, separate the VLAN numbers with a comma and no space, for example, 100,200.

  • To associate multiple ports with a network, separate the port numbers with a comma and no space, for example, 1,2.

  • A network and bridge operate as one entity.

    To delete a network and bridge, click the radio button adjacent to that network and bridge row. Click Delete. The page automatically refreshes; there is no confirmation question. Note that you can delete only one network and bridge at a time.

Step 10

Click Next.

The VM Deployment navigation row shows 4 Configuration highlighted.

(Optional) The Port Forwarding window is displayed.

Step 11

In the Port Number field, enter the number of the port for port forwarding.

Step 12

In the External Port Number field, enter the number of the external port. The external port is accessible only from the WAN bridge.

Step 13

Click Next.

The VM Deployment navigation row shows 5 Review & Deploy as being highlighted.

The following message is displayed: Starting VM deployment. Redirecting to Status Page.
Step 14

Click OK.

The window refreshes and the Status is displayed, showing the VM Status table listing, with columns for VM name, profile name, status, and VNC console.

As the VM is being deployed, the status shows VM in Transient State. After deployment is complete, the status shows VM is running.

Step 15

After deployment is complete, click the Management tab to manage the VM with tasks, including power off, power on, reboot, and delete.

Upgrade and Downgrade Guidelines for Cisco vWAAS and vCM

This section contains the following topics:

Upgrade Guidelines for Cisco vWAAS and Cisco vWAAS Nodes

Considering the following upgrade guidelines for Cisco vWAAS and Cisco vWAAS nodes.

  • When upgrading Cisco vWAAS, do not upgrade more than five Cisco vWAAS nodes at the same time on a single Cisco UCS device. Upgrading more than five Cisco vWAAS nodes at the same time may cause the Cisco vWAAS devices to go offline and to diskless mode.

  • Cisco vWAAS in Cisco WAAS Version 6.4.1x and later requires additional resources before upgrading from Cisco vWAAS in Cisco WAAS Version 6.2.3d to Cisco vWAAS in Cisco WAAS Version 6.4.1x and later.

    • Upgrading from the Cisco WAAS Central Manager: If you initiate and complete the upgrade from the WAAS Central Manager without increasing resources for Cisco vWAAS, alarms (CPU and RAM) to indicate insufficient resource allocation is displayed on the Cisco WAAS Central Manager after the upgrade process is completed. No alarms are displayed at the beginning of the upgrade process.

    • Upgrading from the Cisco WAAS CLI: If you initiate an upgrade to Cisco WAAS Version 6.4.1 with the Cisco WAAS CLI, a warning about insufficient resources is displayed at the start of the upgrade process.

Cisco vWAAS Upgrade and SCSI Controller Type

If needed, change the SCSI Controller Type to VMware Paravirtual by following these steps:

Before you begin

If the virtual host was created using an OVA file of Cisco vWAAS in Cisco WAAS Version 5.0 or earlier, and you have upgraded Cisco vWAAS in Cisco WAAS, you must verify that the SCSI Controller Type is set to VMware Paravirtual. Otherwise, Cisco vWAAS boots with no disk available and fails to load the specified configuration.

Procedure

Step 1

Power down the Cisco vWAAS.
Step 2

From the VMware vCenter, choose vSphere Client > Edit Settings > Hardware.

Step 3

Choose SCSI controller 0.

Step 4

From the Change Type drop-down list, verify that the SCSI Controller Type is set to VMware Paravirtual. If this is not the case, choose VMware Paravirtual.

Step 5

Click OK.

Step 6

Power up the Cisco vWAAS in Cisco WAAS Version 5.2.1 or Cisco WAAS 6.1.x or later. Cisco WAAS Version 6.1.x is the earliest version supported.

Upgrading Cisco vWAAS and vCM-100 with RHEL KVM or KVM on CentOS

Consider the following guidelines for upgrading a Cisco vWAAS or Cisco vCM-100 with RHEL KVM or KVM on CentOS.

If you upgrade to Cisco WAAS Version 5.2.1 or downgrade from Cisco WAAS Version 5.2.1, and use a Cisco vCM-100 model with the following parameters, the Cisco vCM-100 may not come up due to boot order errors in the Globally Unique Identifiers (GUID) Partition Table (GPT).

  • Cisco vCM-100 has default memory size of 2 GB.

  • Cisco vCM-100 uses the RHEL KVM or KVM on CentOS hypervisor.

  • Run the restore factory-default command or run the restore factory-default preserve basic-config command.

  • If you are upgrading a Cisco vCM-100 model to Cisco WAAS Version 5.2.1, the upgrade process on this type of configuration will automatically clear system and data partition.

    • If you upgrade the Cisco vCM device to WAAS Version 5.2.1 via the console: A warning message similar to the following will be displayed:

      WARNING: Upgrade of vCM device to 6.2.0 (or) higher version with ‘/sw’ and ‘/swstore’ size less than 2GB will clear system and data partition.

    • If you upgrade the Cisco vCM device to WAAS Version 5.2.1 using the Cisco WAAS Central Manager GUI, a warning message is not displayed.

  • The restore factory-default command erases the user-specified information that is stored in the flash image, including the starting configuration of the device, and also removes data from the disk, user-defined partitions, and the entire Cisco WAAS Central Manager database.

    To resolve this situation, follow these steps:

    1. Power down the Cisco vWAAS using the virsh destroy vmname command or the virt manager.

    2. Power up the Cisco vWAAS using the virsh start vmname command or the virt manager.


Note

This upgrade scenario or downgrade scenario does not occur for Cisco vCM-100 models whose memory size is upgraded to 4 GB.

Migrating a Physical Appliance Being Used as a Cisco WAAS Central Manager to a Cisco vCM

Procedure

Step 1

Introduce Cisco vCM as the Cisco WAAS Standby Central Manager by registering it with the Cisco WAAS Primary Central Manager.
Step 2

Configure both device and device-group settings through the Cisco WAAS Primary Central Manager and ensure that devices are getting updates. Wait for two to three data-feed poll rates so that the Cisco WAAS Standby Central Manager gets configuration sync from the Cisco WAAS Primary Central Manager.

Step 3

Ensure that the Cisco WAAS Primary Central Manager and Cisco WAAS Standby Central Manager updates are working.
Step 4

Switch over Cisco WAAS Central Manager roles so that Cisco vCM works as Primary WAAS Central Manager. For additional details, see the section "Converting a Standby Central Manager to a Primary Central Manager" in the chapter "Maintaining Your Cisco WAAS System" of the Cisco Wide Area Application Services Configuration Guide.