Virtual WAAS (vWAAS) implements a virtual WAAS appliance in VMware ESXi on a host server such as Cisco UCS.

NOTE: vWAAS was introduced in WAAS version 4.3.1. This section is not applicable to earlier WAAS versions.

Identifying a vWAAS Device

You can identify a vWAAS device from the Manage Devices page of the WAAS Central Manager. The device type appears as OE-VWAAS for all types of vWAAS devices. The show version and show hardware CLI commands also show the device Version as OE-VWAAS.

Figure 1. vWAAS Device Type

The model of the vWAAS device is determined from the number of CPUs and Maximum TCP Connections shown in the Device Dashboard window when you select the device from the Manage Devices page. These two fields are displayed only for vWAAS devices.

Figure 2. vWAAS Capabilities

The models are as follows:

vWAAS-750: 2 CPUs, 750 maximum TCP connections

vWAAS-6000: 4 CPUs, 6000 maximum TCP connections

vWAAS-12000: 4 CPUs, 12000 maximum TCP connections

vCM-100N: 2 CPUs, 100 maximum nodes

vCM-2000N: 4 CPUs, 2000 maximum nodes

For vCM devices, you can use the show hardware command to determine the number of CPUs, which tells you which model of vCM is installed.

Note: The vWAAS device shows 2 disks installed. The first, disk00, is 4 GB and emulates the flash storage in a physical WAAS device. The second, disk 01, emulates the hard disk in a physical WAAS device and varies in size depending on the vWAAS model.

The show tfo detail command also displays the maximum TCP connection limit:

vWAAS device registration and deregistration is logged in the system message log with a line that begins with "vWAAS:". You can view the system message log in the Central Manager by choosing Admin > Logs > System Messages.

Figure 3. vWAAS Registration Syslog Message

Verifying vWAAS Virtual Interfaces

Two virtual interfaces are available on vWAAS devices.

In the Central Manager device> Configure > Network > Network Interfaces page, the vWAAS interface type appears as Virtual (Port Channel, Standby, Inline, and GigabitEthernet are not applicable), which is similar to the GigabitEthernet . Some of the GigabitEthernet interface options, such as Port Channel, autosense, speed, mode, and standby, do not apply to virtual interfaces.

You can also see the virtual interfaces with the show running-config command:

Troubleshooting vWAAS Networking

If you see no connections on the vWAAS device, check the vWAAS networking configuration in the vSphere Client. Is the vWAAS device connected to the correct vSwitch?

Using the vSphere Client, you can trace vWAAS network connectivity from the device page. Identify which network label the network adapter is connected to, determine the virtual switch that this network is connected to, and determine the physical NIC that is a member of this virtual switch. Verify that the configuration is correct.

Also make sure the virtual switch VLAN settings are correctly configured to reach the network.

From the vWAAS device, ping the default gateway and Central Manager to make sure they are reachable.

Troubleshooting VPATH Interception

A vWAAS device can use VPATH or WCCP interception methods, but not both. To check if VPATH interception is enabled from the Central Manager, choose the vWAAS device, then choose Configure > Interception > VPATH. If the Enable VPATH box is checked, then it is enabled. WCCP must be disabled before VPATH can be enabled.

You can use the vn-service vpath global configuration command to enable or disable VPATH interception.

From the vWAAS device CLI, you can view VPATH status and statistics with the show statistics vn-service vpath command: