Installing and Configuring Cisco Packaged Contact Center Enterprise 9.0(x)
Tasks Common to Virtual Machine Creation
Downloads: This chapterpdf (PDF - 1.22MB) The complete bookPDF (PDF - 4.59MB) | The complete bookePub (ePub - 1.13MB) | Feedback

Tasks Common to Virtual Machine Creation

Tasks Common to Virtual Machine Creation

These tasks are common to many golden template and direct-install procedures. The applicability (golden template or direct-install, or both) is noted at the start of each task.

Select Open Virtualization Format File

Open Virtualization Format files (OVAs) are downloaded and extracted from Cisco.com and are required for both golden templates and direct installs. The OVAs define the basic structure of the corresponding VMs that are created—including the CPU, RAM, disk space, reservation, for CPU and reservation for memory.

This table shows the OVA that is used for each Cisco Systems contact center product.

Software OVA
Cisco Unified Contact Center Enterprise CCE Call Server and Data server CCE-PAC-M1-CCE-vmv8-v9.0.1.ova
Customer Voice Portal (CVP) Call/VXML, and OAMP servers CCE-PAC-M1-CVP-vmv8-v9.0.1.ova
Customer Voice Portal (CVP) reporting server CCE-PAC-M1-CVP-Reporting-Server-vmv8-v9.0.1.ova
Cisco Unified Communications Manager (CUCM) publisher and subscriber cucm_9.1_vmv8_v1.7.ova
Cisco Unified Intelligence Center (CUIC) publisher and subscriber CCE-PAC-M1-IntelligenceCenter-vmv8-fv2.1-v9.0.ova
Cisco Finesse primary and secondary CCE-PAC-M1-Finesse-vmv8-9.0.1.ova

Create a Virtual Machine from the OVA

Procedure
    Step 1   Select the Host in the vSphere client.
    Step 2   Choose File > Deploy OVF Template.
    Step 3   Browse to the location on your local drive where you stored the OVA. Click Open to select the file. Click Next.
    Step 4   Click Next at the OVF Template Details page.
    Step 5   Enter the virtual machine name. It cannot contain spaces or special characters. Enter a maximum of 32 characters. Click Next.
    Step 6   On the Deployment Configuration page, use the drop-down to select the appropriate configuration. Then click Next.
    Step 7   Choose a datastore on which to deploy the new virtual machine. Then click Next.

    For each datastore, the tables below describe the RAID group, the ESXi Host, and the virtual machines for the server.

    RAID configuration for the C240 M3S

    RAID Group

    VM Datastore

    ESXi Host

    Virtual Machines

    VD0

    datastore1

    A

    ESXi operating system

    Unified CCE Data Server, Side A

    VD1

    datastore2

    A

    Unified CCE Call Server, Side A

    Unified CVP Server 1A

    Unified CVP Server 2A

    Unified Intelligence Center Server pubisher

    Unified CVP OAMP Server

    Unified Communications Manager Publisher

    Unified Communications Manager Subscriber 1

    Cisco Finesse Primary

    VD0

    datastore1

    B

    ESXi operating system

    Unified CCE Data Server, Side B

    VD1

    datastore2

    B

    Unified CCE Call Server, Side B

    Unified CVP Server 1B

    Unified CVP Server 2B

    Unified Intelligence Center Server (subscriber)

    Unified Communications Manager Subscriber 2

    Unified CVP Reporting Server (optional)

    Cisco Finesse secondary

    RAID configuration for the C260 M2

    RAID Group

    VM Datastore

    ESXi Host

    Virtual Machines

    Drive Group 0

    datastore1

    A

    ESXi operating system

    Drive Group 1

    datastore2

    A

    Unified CCE Call Server, Side A

    Unified CVP Server 1A

    Unified CVP 2A

    Unified Intelligence Center Server pubisher

    Unified CVP OAMP Server

    Unified Communications Manager Publisher

    Unified Communications Manager Subscriber 1

    Cisco Finesse Primary

    Drive Group 2

    datastore3

    A

    Unified CCE Data Server, Side A

    Drive Group 0

    datastore1

    B

    ESXi operating system

    Drive Group 1

    datastore2

    B

    Unified CCE Call Server, Side B

    Unified CVP Server 1B

    Unified CVP Server 2B

    Unified Intelligence Center Server (subscriber)

    Unified Communications Manager Subscriber 2

    Unified CVP Reporting Server (optional)

    Cisco Finesse secondary

    Drive Group 2

    datastore3

    B

    Unified CCE Data Server, Side B

    Step 8   On the Disk Format page, keep the default virtual disk format: Thick provisioned Lazy Zeroed format. Click Next.
    Step 9   Confirm that the Network Mapping page is correct for the CCE Call Server and Data Server:
    1. For the Call Server and the Data Servers:
      • Map Public to UCCE Public Network
      • Map Private to UCCE Private Network
    2. For all other servers, map Public to UCCE Public Network.
    Step 10   At the Successfully Completed message, click Close.

    Install Antivirus Software

    Perform this procedure for both golden-template and for direct-install options.

    This procedure is required for the applications that use the Windows 2008 Operating System.

    Install one of the following anti-virus software products for Unified CCE Call Server, the Unified CCE Data Server, the Unified CVP server, the Unified CVP OAMP server, and the Unified Reporting server.

    • McAfee® VirusScan® Enterprise 8.7i / 8.8i
    • Symantec® Endpoint Protection 11.0 / 12.1
    • Trend Micro Server Protect Version 5.7 / 5.8
    Important:

    Update anti-virus software manually. Do not enable automatic updates.


    Tip


    To allow required access to installation program files or folders, perform file-blocking exclusions in the anti-virus product file-and-folder protection rules. To do this in McAfee VirusScan:
    • Launch the VirusScan console.
    • Right-click Access Protection and select Properties.
    • In the Anti-virus Standard Protection category, make sure that the rule Prevent IRC communication is unchecked in the Block column.

    Important:

    Packaged Contact Center Enterprise supports Symantec Endpoint Protection 12.1.

    Be aware that in the firewall component of Symantec Endpoint Protection 12.1, the Network Threat Protection feature, must be disabled. If the feature remains enabled, which is the default, both sides of a duplexed router come up in simplex mode, thus blocking communication between each side of a router. This blocking impacts all deployment types.

    If you retain the default (enabled) and start services on side A and B of the router, a Symantec message pops up in the system tray indicating: The client will block traffic from IP address [side A router address] for the next 600 seconds(s). The same message is also written to the security log in client management. The Symantec Network Threat Protection traffic log indicates that a default firewall rule called “Block_all” was dynamically enabled. The result, according to the router logs, is that both sides of the router come up in simplex mode.

    To resolve the issue, you must disable the Symantec firewall and restart both sides of the router. To do this, double click the Symantec icon in the system tray and select Change Settings. Then configure settings for Network Threat Protection and uncheck the Enable Firewall check box at the top of the Firewall tab.

    Install VMware Tools

    VMware Tools is a suite of utilities that enhance the performance of the virtual machine guest operating system and improve management of the virtual machine.

    Perform this procedure for both golden-template and for direct-install options.

    Procedure
      Step 1   Right-click the VM menu. Select Guest > Install / Upgrade VMware tools.
      Step 2   Wait for the popup window (this may take time) and accept the default Automatic Tools Upgrade.
      Step 3   Click OK.
      Step 4   Restart if you are prompted to do so.
      Note    VMWare Tools should be installed in all VMs

      Convert the Virtual Machine to a Golden Template

      Perform this procedure for the golden-template install option. This procedure is not necessary for the direct-install option.

      Note


      VMware uses the term Template. Packaged CCE uses the term Golden Template for templates consisting of application and operating systems that are used for CCE PAC M1.


      Before You Begin

      Ensure that the template virtual machine is in the WORKGROUP.

      Procedure
        Step 1   If the VM is not already powered off, from the VM menu, select Power > Shut down the guest.
        Step 2   From the VMware vCenter Inventory menu, right-click the virtual machine and choose Template > Convert to Template.

        Mount and Unmount ISO Files

        Upload ISO image to data store:

        1. Select the host and click Configuration. Then click Storage in the left panel.
        2. Select the datastore that will hold the ISO file.
        3. Click Browse this datastore.
        4. Click the Upload icon and select Upload file.
        5. Browse to the location on your local drive where you saved the ISO file, and upload the ISO to the datastore.

        Mount the ISO image:

        1. Right-click the VM and select Edit virtual machine settings.
        2. Click Hardware and select CD|DVD Drive 1.
        3. Check Connect at power on (Device status panel upper right).
        4. Click the Datastore ISO File radio button and then click Browse.
        5. Navigate to the data store where you uploaded the file.
        6. Select the ISO.

        Unmount the ISO image:

        1. Right-click the VM and select Edit virtual machine settings.
        2. Click Hardware and select CD|DVD Drive 1.
        3. Uncheck Connect at power on (Device status panel, upper right).

        Configure DNS Server

        Procedure
          Step 1   Log in to the DNS server.
          Step 2   Click Start > Administrative Tools > DNS. This opens the DNS Manager.
          Step 3   In the Forward lookup zone, navigate to the domain name you have provided in the automation excel sheet.
          Step 4   Right-click the domain name and select New Host (A or AAAA).
          Step 5   In the New Host dialog box, enter the computer name and IP address of the VOS products. Click Add Host.
          Step 6   The DNS manager automatically creates a New Host record in the Reverse Lookup Zones.
          Step 7   Check whether the Added Host exists in the Forward and Reverse Lookup Zones.

          Configure Autogrowth

          When you created the Data Servers for Side A and Side B, you installed Microsoft SQL Server and enabled autogrowth for the tembdb. For this release, autogrowth settings for the logger on Side A and Side B are also updated automatically. However, you must manually enable autogrowth for the aw databases on Side A and Side B, any external aw database, any external hds databases, and the Outbound Option database on Side A.

          Before You Begin

          You can perform this step after the databases are created.

          Procedure
            Step 1   Select Start > All Programs > Microsoft SQL Server > SQL Server Management Studio.
            Step 2   Click Databases > System Databases.
            Step 3   Right-click the database.
            1. For Side A, select the <instance>_ awdb database and the <instance>_sideA database. If you have enabled Outbound option, select <instanceName>_baA database.
            2. For Side B, select the <instance>_ awdb and the <instance>_sideB database.
            3. For any external AW-HDS-DDS systems, select <instance>awdb and <instanceName>_hds database.
            Step 4   For each database, select Properties.
            Step 5   For each file:
            1. For the date file, set In Megabytes to 100.
            2. For the log file, set In Percent to 10.
            Step 6   Click OK.