
+-----------------------------------------------------------------------------------+
| CISCO CUSTOMER COLLABORATION PLATFORM (CCP) 15.0(1) VIRTUAL SERVER TEMPLATE (OVA) |
+-----------------------------------------------------------------------------------+

1.0 OVERVIEW
2.0 SCOPE
3.0 DEPLOYMENT OPTIONS
4.0 INSTALLATION INSTRUCTIONS
5.0 CHANGELOG
6.0 NOTES
7.0 TRADEMARKS AND NOTICES


1.0 OVERVIEW
------------
The Cisco CCP 15.0(1) Virtual Server Template (OVA) defines a virtual machine configuration that
is supported in the CCP 15.0(1) release. This OVA contains all supported virtual machine
configurations of this release. Any fresh installation of CCP 15.0(1) must use a virtual machine
created from this OVA.


2.0 SCOPE
---------
The template is an OVA (open virtual appliance) file that can be imported/deployed using the OVF (Open
Virtualization Format) support of VMware. The OVA file defines the following for the virtual machine
based on the deployment selected:

    - Number of virtual CPUs
    - Amount of RAM
    - Number and size of hard disks
    - ESXi support: ESXi 7.0 and later
    - OS Support: Alma 8 (64-bit)

3.0 DEPLOYMENT OPTIONS
----------------------
There are two available deployment options:

    - CCP Large Deployment

        Virtual Machine Template for CCP Large Deployment Profile.

        Details:
        Alma 8 (64-bit)
        CPU: 4 vCPU with 8000 MHz reservation
        Memory: 14 GB with 14 GB reservation
        Disk 1: 146 GB disk
        Disk 2: 256 GB disk

    - CCP Small Deployment

        Virtual Machine Template for CCP Small Deployment Profile.

        Details:
        Alma 8 (64-bit)
        CPU: 2 vCPU with 4390 MHz reservation
        Memory: 10 GB with 10 GB reservation
        Disk 1: 80 GB disk
        Disk 2: 80 GB disk


4.0 INSTALLATION INSTRUCTIONS
-----------------------------
Import the OVA using the vSphere Client:

    1) Select File --> Deploy OVF Template to start the import.

    2) Navigate to and select the OVA file downloaded from Cisco.

    3) Provide the VM name, and then select the server and the data store.

    4) Verify the deployment settings and finish the deployment.

    5) After the VM is created, proceed with CCP installation.


5.0 UPGRADE INSTRUCTIONS
------------------------
Instructions to update the Guest OS and memory:
1) Power of the VM.
2) Right click "Edit settings".
3) In "Virtual Hardware" tab, Update the memory and reservation based on large and small deployment mentioned above.
4) In "VM Options" tab, under General update the OS to Other Linux(64bit)

Instructions to upgrade the virtual hardware version:

Below is an example list of steps to accomplish this process. Depending on
the specific version of ESXi in your environment and other variables, some of
these steps may vary slightly.

NOTE: PERFORM ONLY ON VMS RUNNING ON ESXi HOST 7.0 AND ABOVE.
NOTE: If these changes are done on VMs running on ESXi host lower than 7.0, the VMs will fail to boot.
        1) Navigate to the Summary tab for the VM in question, right-click the Storage volume on which the VM is located, and choose "Browse this datastore".
        2) In the "Datastore Browser" window, locate and select the relevant folder for the VM in question.
        3) Right-click on the <virtual_machine_name>.vmx file and choose "Download...", select a folder on your local machine for the file.
        4) Make a backup copy of the .vmx file on your local machine by running the following commands from a Windows Command Prompt in the same folder as the downloaded .vmx file. If your edits break the virtual machine,you can roll back to the original version of the file.
                copy"<virtual_machine_name>.vmx""<virtual_machine_name>.vmxBACKUP"
        5) Modifiy the configuration file-".vmx file":
                Locate the entry for virtualHW.version.
                Change the entry to:
                virtualHW.version = "17"
        6) Upload the edited <virtual_machine_name>.vmx file to the Datastore by selecting the relevant folder for the VM in question in the "Datastore Browser" window, clicking the button for "Upload files to this datastore", and choosing "Upload File..."
        7) Locate the edited <virtual_machine_name>.vmx file from your local machine and select it, acknowledging that existing files of the same name will be overwritten
             Note: Keep the "Datastore Browser" window open, as you will need it again in Step 10
        8) Now that .vmx file is updated, note on which ESXi host the VM in question is located.
        9) From the main vSphere client window, right-click the VM in question in the list of VMs and choose "Remove from Inventory"
        10) Navigate back to the "Datastore Browser" (from the window left open earlier. Otherwise, open the Datastore Browser from another VM's Summary page "Storage" list or the ESXi host 's Summary page "Storage" list)
        11) Locate and select the relevant folder for the VM in question
        12) Right-click on the <virtual_machine_name>.vmx file and choose "Add to Inventory".
        13) Step through the "Add to Inventory" wizard, selecting the same host on which you previously noted the VM was located. These steps will ensure that the VM will utilize the updated .vmx file using the virtual hardware version 17.
        14) On the newly-readded VM you can verify the change by navigating to the summary tab and noting the VM Version field.

6.0 CHANGELOG
-------------
The following are changes from the OVA in the previous release:

	1) OS changed to Alma 8 (64-bit)
	
	2) Virtual Hardware Version changed to 17, this is supported on ESXi version 7.0 and greater.

	3) RAM memory updated for both small and large deployment.


7.0 NOTES
---------
1) Operating System version is changed to Alma 8 (64-bit)

2) Network Adapter type is selected to be VMXNET3 to get the best performance.

3) Video Card memory size is set to 8 MB


8.0 TRADEMARKS AND NOTICES
--------------------------
Copyright© 2025 Cisco Systems, Inc. All Rights Reserved.
