Tar Archive Package for vWAAS on KVM for WAAS Version 5.x to 6.2.x
For vWAAS on KVM, for WAAS Version 5.x through 6.2.x, Cisco provides a tar archive or NPE tar archive package for each vWAAS connection profile (examples shown in Table 6-3) and for each 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 on NFVIS (Network Functions Virtualization Infrastructure Software). For more information on Cisco NFVIS and Cisco NFV (Network Functions Virtualization), see the Cisco Enterprise Network Functions Virtualization Solution Overview. For more information on vWAAS on NFVIS, see Chapter 9, “Cisco vWAAS with Cisco Enterprise NFVIS” .
Note For a listing of hypervisor OVA, zip, and tar.gz files for vWAAS, see the Cisco Wide Area Application Services (WAAS) Download Software Page and select the WAAS software version used with your vWAAS instance.
Table 6-3 OVA Package Format Examples for vWAAS on RHEL KVM for WAAS Version 5.x to 6.2.x
|
|
Cisco KVM 150 package file Cisco KVM 150 package file for NPE |
- Cisco-KVM-vWAAS-150-6.2.3d-b-68.tar.gz
- Cisco-KVM-vWAAS-150-6.2.3d-b-68-npe.tar.gz
|
Cisco KVM 200 package file Cisco KVM 200 package file for NPE |
- Cisco-KVM-vWAAS-200-6.2.3d-b-68.tar.gz
- Cisco-KVM-vWAAS-200-6.2.3d-b-68-npe.tar.gz
|
Cisco KVM 750 package file Cisco KVM 750 package file for NPE |
- Cisco-KVM-vWAAS-750-6.2.3d-b-68.tar.gz
- Cisco-KVM-vWAAS-750-6.2.3d-b-68-npe.tar.gz
|
Cisco KVM 1300 package file Cisco KVM 1300 package file for NPE |
- Cisco-KVM-vWAAS-1300-6.2.3d-b-68.tar.gz
- Cisco-KVM-vWAAS-1300-6.2.3d-b-68-npe.tar.gz
|
Cisco KVM 2500 package file Cisco KVM 2500 package file for NPE |
- Cisco-KVM-vWAAS-2500-6.2.3d-b-68.tar.gz
- Cisco-KVM-vWAAS-2500-6.2.3d-b-68-npe.tar.gz
|
Cisco KVM 6000 package file Cisco KVM 6000 package file for NPE |
- Cisco-KVM-vWAAS-6000-6.2.3d-b-68.tar.gz
- Cisco-KVM-vWAAS-6000-6.2.3d-b-68-npe.tar.gz
|
Table 6-4 Cisco OVA Package Formats for vCM for WAAS Version 5.x to 6.2.x
|
|
Cisco KVM 100N package file Cisco KVM 100N package file for NPE |
- Cisco-KVM-vCM-100N-6.2.3d-b-68.tar.gz
- Cisco-KVN-vCN-100N-6.2.3d-npe-b-68-npe.tar-gz
|
Table 6-5 Installation Files for vWAAS on KVM and vWAAS on NFVIS for WAAS 5.x to 6.2.x
|
|
|
- Cisco signature envelope file
Verifies that this deployment is from Cisco.
|
X |
X |
- Manifest file with checksums
|
X |
X |
- image_properties.xml
A VM configuration template file used on the Cisco NFVIS platform.
|
|
X |
- 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.
|
|
X |
- INSTRUCTIONS.TXT
Describes the procedure for deploying the virtual instance and for using the launch.sh file.
|
X |
|
|
X |
|
- vm.xml
Configuration file needed for vWAAS deployment using virtual bridge or Open Virtual Switch (OVS) present in host mac.
|
X |
|
- VM disk images
A 4 GB flash disk, 10 GB system disk, and data disk (data disk size is dependent on your connection profile).
|
X |
X |
|
X |
|
Using the Launch Script to Deploy vWAAS on KVM for 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 vWAAS VM. (You must have root permissions to launch the 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 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 vWAAS, run the launch.sh script:
a. To check the prerequisite conditions, use the./launch.sh check command.
b. To launch 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 in working state.
c. To launch vWAAS using macvtap, use the./launch.sh vm-name macvtap interface1-name interface2-name command,
- vm-name—The specified name of the vWAAS VM.
- interface1-name and interface2-name—The specified Ethernet interfaces of the host machine.
Step 6 The vWAAS is launched
Step 7 To view the vWAAS, use the VM GUI or the virsh list command.
Step 8 To connect to the console, use the VM GUI or the virsh console vm-name command.
Step 9 To power down the vWAAS, use the virsh destroy vm-name command.
Step 10 To undefine the vWAAS:
a. Use the virsh undefine vm-name command.
b. Remove the directory with the specified vm-name.
Note If you want to create another vWAAS of the same model, follow this procedure again for a different vWAAS. 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 vWAAS on KVM on UCS-E for WAAS Version 5.x to 6.2.x
Use the EzDeploy script for simplified deployment of a vWAAS. Note that the EzDeploy script is not used for the vCM.
The following are prerequisites for launching the EzDeploy script:
- To launch the 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 WAAS CM registration status)
– There is enough disk and RAM memory to deploy another vWAAS.
– Compatibility of software versions.
– Availability and readiness of network connectivity.
Note Because EzDeploy leverages the launch.sh script to launch a 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 UCS-E, follow these steps:
Step 1 Launch the 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 hte ezdeploy.sh, you are prompted for bootstrap configuration parameters:
– vWAAS KVM name—The name is dependent on whether or not you provide the vWAAS’ bootstrap configuration.
If you do not provide the vWAAS’ bootstrap configuration, the name is set as the name of the guest KVM to be created. not the vWAAS’ host name.
If you provide the vWAAS’ bootstrap configuration, vWAAS’ host name is set and used in both instances.
– vWAAS’ local IP address and mask
– Default GW IP address: an address on the ISR-4000 series RP reachable by the vWAAS and having external network connectivity
– IP address of the WAAS CM with which the vWAAS will register
– One NTP server address, without authentication. If you want to have authentication or multiple NTP servers, use the WAAS CM to configure these after the 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 file bootstrap-cfg.xml in the directory created for this KVM.
– The execution log and error log of the script are saved in the file ezdeploy-log.txt in the directory created for this KVM.
– For the 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, so 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 completion of the EzDeploy script, the vWAAS is fully up and running. Registration with the specified WAAS CM and the NTP server are automatically started after installation of their corresponding CLIs.
d. To view the vWAAS, use the VM GUI or the virsh list command.
e. To connect to the console, use the VM GUI or the virsh console vm-name command.
f. To power down the vWAAS, use the virsh destroy vm-name command.
g. To undefine the vWAAS:
– Use the virsh undefine vm-name command.
– Remove the directory with the specified vm-name.