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
|
|
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 Cisco vCM in Cisco 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 Cisco vWAAS on RHEL KVM and Cisco vWAAS with Cisco NFVIS in WAAS 5.x to 6.2.x
|
|
|
- Cisco signature envelope file
Verifies that this deployment is from Cisco.
|
Yes |
Yes |
- Manifest file with checksums
|
Yes |
Yes |
- image_properties.xml
A VM configuration template file used on the Cisco NFVIS platform.
|
No |
Yes |
- 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.
|
No |
Yes |
- INSTRUCTIONS.TXT
Describes the procedure for deploying the virtual instance and for using the launch.sh file.
|
Yes |
No |
|
Yes |
No |
- vm.xml
Configuration file needed for vWAAS deployment using virtual bridge or Open Virtual Switch (OVS) present in host mac.
|
Yes |
No |
- VM disk images
A 4 GB flash disk, 10 GB system disk, and data disk (data disk size is dependent on your connection profile).
|
Yes |
Yes |
|
Yes |
No |
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)
–
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.