Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide, Release 10.0(x)
Prepare Customer Site Servers
Downloads: This chapterpdf (PDF - 1.29MB) The complete bookPDF (PDF - 4.0MB) | The complete bookePub (ePub - 806.0KB) | Feedback

Prepare Customer Site Servers

Prepare Customer Site Servers

Perform all the procedures in this section on the Side A and the Side B servers.

Configure RAID for the C240 MS3 TRC#1

For each array created using this procedure, use the following settings:
  • Stripe size: 128KB
  • Read Policy: Read Ahead Always
  • Write Policy: Write Back with BBU
Procedure
    Step 1   Power on the UCS server, making sure that Quiet Boot is disabled in BIOS.
    Step 2   Press Ctrl-H during the initial startup sequence to enter the MegaRAID BIOS configuration utility.
    Step 3   Click Start.
    Step 4   Select Configuration Wizard on the left panel. Click New Configuration. Then click Next.
    Step 5   At the prompt to clear the configuration, click Yes.
    Step 6   Select Manual Configuration. Then click Next.
    Step 7   On the next screen, in the left panel, add the first eight drives to create Drive Group0 as follows:
    1. Select drives 1 - 8.
    2. Click Add to Array.
    3. Click Accept DG.
    Step 8   Add the remaining eight drives to create Drive Group1 as follows:
    1. On the left panel, select drives 9 - 16.
    2. Click Add to Array.
    3. Click Accept DG.
    4. Click Next to accept the Drive Group.
    Step 9   Add Drive Group0 to a span as follows:
    1. Select Drive Group0.
    2. Click Add to Span.
    3. Click Next.
    Step 10   Configure RAID for Drive Group0 as follows:
    1. For RAID Level, select RAID 5.
    2. For Stripe Size, select 128KB.
    3. For Read Policy, select read ahead = always.
    4. For Write Policy, select write back with bbu.
    5. Click Update Size to finalize the RAID volume and to determine the size of the resulting volume. It resolves to 1.903TB
    6. Click Accept to accept the virtual drive definition, VD0.
    7. Click Next.
    8. Click Back to add the second RAID 5 array.
    Step 11   Click Back to add the second RAID 5 array as follows:
    1. Select Drive Group1.
    2. Click Add to Span.
    3. Click Next.
    Step 12   At the RAID Selection screen:
    1. For RAID Level, select RAID 5.
    2. For Strip Size, select 128KB.
    3. For Read Policy, select read ahead = always.
    4. For Write Policy, select write back with bbu.
    5. Click Update Size. The size resolves to 1.903TB
    6. Click Accept to accept the virtual drive definition, VD1.
    Step 13   Click Yes at the BBU warning screen.
    Step 14   Click Next at the Virtual Live Definition screen to indicate that you have finished defining virtual drives.
    Step 15   Click Accept at the Configuration Preview screen to accept the RAID configuration.
    Step 16   Click Yes to save the configuration.
    Step 17   Click Yes to start drive configuration.
    Step 18   Click Home to exit the Wizard when both drives report their status as Optimal.
    Step 19   Click Exit.

    After RAID configuration is complete on the drives, the system may try to initialize (format) the new RAID array. When this happens, the current initialization progress can be seen from the Web BIOS screen. Wait for the background initialization to complete before proceeding with any of the subsequent server configuration steps such as installing ESXi.

    You can check background initialization progress on either the Web BIOS Home screen or Virtual Drives screen.


    Configure RAID for C260 M2 TRC#1

    For each array created using this procedure, use the following settings:
    • Stripe size: 128KB
    • Read Policy: Read Ahead Always
    • Write Policy: Write Back with BBU
    Procedure
      Step 1   Power on the UCS server.
      Step 2   Press Ctrl-H during the initial startup sequence to enter the Adapter Selection screen for RAID BIOS configuration utility.
      Step 3   Click Start to launch the RAID BIOS Config Utility.
      Step 4   At the page to pick the appropriate configuration type, select the button for New Configuration. Then click Next.
      Step 5   At the page to select the configuration method, select the button for Manual Configuration. Make sure the Redundancy drop-down list shown Redundancy when possible. Then click Next.
      Step 6   On the Drive Group Definition page, on the left panel, select Slot 1 and Slot 2.
      1. Click Add to Array. This moves them to the Drive Groups panel.
      2. Click Accept DG. This creates Drive Group 0.
      Step 7   On the left panel, select the next 8 slots.
      1. Click Add to Array. This moves them to the Drive Groups panel.
      2. Click Accept DG. This creates Drive Group 1.
      Step 8   On the left panel, select the last 6 slots.
      1. Click Add to Array. This moves them to the Drive Groups panel.
      2. Click Accept DG. This creates Drive Group 2.
      3. Click Next to advance to the Span Definition page.
      While you create the Drive Groups, if you see a message asking if you are sure you want to select Write Back with BBU mode, click Yes. You have now created three Drive Groups. You now create virtual drives using these Drive Groups.
      Step 9   On the Span Definition page, select Drive Group 0.
      1. Click Add to Span.
      2. Click Next to open the Virtual Drive Definition screen.
      3. On the Virtual Drive Definition page for Drive Group 0, change only the Select Size field. In Select Size, enter 278.464 GB, making sure to type the digits at the far left of the field (leaving no spaces before the 2). Then click Accept.
      4. Click Back to return to the Span Definition page.
      Step 10   On the Span Definition page, select the second Drive Group.
      1. Click Add to Span.
      2. Click Next to open the Virtual Drive Definition screen.
      3. Change the RAID level from RAID 1 to RAID 5.
      4. For Select Size, enter 1.903 TB.
      5. Click Accept.
      6. Click Back to return to the Span Definition page.
      Step 11   On the Span Definition page, select the final Drive Group.
      1. Click Add to Span.
      2. Click Next to open the Virtual Drive Definition screen.
      3. Change the RAID level from RAID 1 to RAID 5.
      4. For Select Size, enter 1.359 TB.
      5. Click Accept.
      6. Click Back to return to the Span Definition page.
      Step 12   On the Virtual Drives screen, verify that the Virtual Drives panel shows RAID 1 (278.454GB), RAID 5 (1.903 TB) and RAID 5 (1.358 TB). Then click Go.

      Install VMware vSphere ESXi

      Packaged CCE uses standard installation procedures, which you can find using VMware documentation (VMware site) for the given version supported with the release of Packaged CCE you are installing.

      Packaged CCE has no unique requirements other than that ESXi should be installed on the first drive, as the default boot drive for the server.

      Add Datastores to the Host Server

      After installing vSphere ESXi, add the remaining datastores. Refer to the vSphere Storage Guide for the vSphere ESXi version in your deployment, available at https:/​/​www.vmware.com/​support/​pubs/​.

      Add Customer ESXi Host to the vCenter

      Refer to the vCenter Server and Host Management documentation at https:/​/​www.vmware.com/​support/​pubs/​


      Note


      vCenter is required for Golden Templates only.


      Customers without vCenter can install on management desktops to administer the Packaged CCE servers.

      Run RAID Config Validator Utility

      After you set up RAID configuration and add the datastores, run this utility to ensure your datastore configuration is correct.

      Procedure
        Step 1   Download the Packaged CCE RAID Config Validator utility from the Packaged CCE Download Software > Deployment Scripts page at http:/​/​software.cisco.com/​download/​type.html?mdfid=284360381&i=rm The utility is a zip file that can be extracted locally and run on any computer that has the Java jre or jdk installed.
        Step 2   Open the Windows command prompt and change to the directory where you downloaded the file. Then type this command java -jar PackagedCCEraidConfigValidator-10.0.jar <IP Address of the Side A server> <username> <password> to run to the tool.
        For example:
        C:\Users\Administrator\Desktop>java -jar PackagedCCEraidConfigValidator-10.0.jar xx.xx.xxx.xxx userName password
        Messages appear on the monitor to show that the validation is starting.

        You see an indication of a valid or invalid configuration.

        Errors include:
        • Non-supported server found or used.
        • Incorrect number of datastores found.
        • Incorrect sizes set for the datastores.
        Step 3   Repeat step 2, entering the IP address of the Side B server in Step 3.

        What to Do Next

        If the utility reports an invalid configuration, you must recreate the RAID configuration. To do this, you need to reset the RAID configuration, re-install ESXi, and then re-run the RAID Config Validator utility to revalidate the configuration.

        NTP and Time Synchronization

        Packaged CCE requires that all parts of the solution have the same time. While time drift occurs naturally, it is critical to configure NTP to keep solution components synchronized.

        To prevent time drifts on Live Data reports, the NTP settings on the Data Server VMs, the Call Server VMs, and on the Cisco Unified Intelligence Center Publisher and Subscriber VMs must be synchronized.

        Windows Active Directory Domain

        The Windows Active Directory PDC emulator master for the forest in which the Packaged CCE domain resides (whether same, parent, or peer) must be properly configured to use an external time source. This external time source should be a trusted and reliable NTP provider, and if already configured for the customer's forest, must be used (and useable) as same source for all other applications as detailed in this section for the Packaged CCE solution.

        See the following references for properly configuring Windows Active Directory Domain for NTP external time source:

        Microsoft Windows Server Domains do not automatically recover or fail over the authoritative internal time source for the domain when the PDC emulator master server is lost, due to hardware failure or otherwise. This article, Time Service Configuration on the DCwith PDC Emulator FSMO Role, helps describe how you must additionally configure the new target server to be the authoritative internal time source for the domain. It also covers manual intervention to recover and seize or reassign the PDC FSMO role to another domain controller.

        Windows Components in the Domain

        Windows hosts in the domain are automatically configured to synch their time with a PDC emulator, whether by the PDC emulator master with authoritative internal time source or chained from same in the domain forest hierarchy.

        Windows Components Not in the Domain

        Use the following steps to set NTP time source for a Windows Server that is not joined to a domain:
        1. In the Command Prompt window, type the following line and press ENTER: w32tm /config /manualpeerlist:PEERS /syncfromflags:MANUAL

          Note


          Replace peers with a comma-separated list of NTP servers.
        2. Restart the w32time service: net stop w32time && net start w32time.
        3. Synch w32time service with peers: w32tm /resync.
        4. Use the following Service Control command to ensure proper start of the w32time service on any reboot of the server: sc triggerinfo w32time start/networkon stop/networkoff.

        ESXi Hosts

        All Packaged CCE ESXi hosts (including those for optional components), must point to the same NTP server(s) used by the Windows domain PDC emulator master as the their external time source.

        Cisco Integrated Service Routers

        Cisco IOS Voice Gateways must be configured to use the same NTP source for the solution in order to provide accurate time for logging and debugging. See Basic System Management Configuration Guide, Cisco IOS Release 15M&T: Setting Time and Calendar Services.

        VOS Components

        Components such as Unified Intelligence Center, Finesse, Social Miner, and Unified Communications Manager must point to the same NTP servers as the domain authoritative internal time source.

        CLI commands for NTP Servers

        While NTP servers are typically specified at install time, here a few commands you can use from the platform cli of the above listed components, to list, add and remove ntp servers. From the platform CLI:
        • To list existing ntp servers: utils ntp servers list
        • To add an additional ntp server: utils ntp server add <host or ip address to add>
        • To delete an existing ntp server: utils ntp server delete (row number of the item to delete). Press Enter.