MediaSense User Guide
Install or Upgrade MediaSense
Downloads: This chapterpdf (PDF - 1.33MB) The complete bookPDF (PDF - 3.24MB) | Feedback

Install or Upgrade MediaSense

Install or Upgrade MediaSense

This chapter contains sections for installing and upgrading Cisco MediaSense.

Install Cisco MediaSense

Procedures in this section describe how to install Cisco MediaSense and the Cisco Unified Communications Operating System (Unified OS). You install both with one program.

Pre-installation tasks and tools

As a first step, verify that you are using hardware and software that Cisco supports. For a list of supported hardware and software, see the Solution Reference Network Design for Cisco MediaSense guide at http:/​/​www.cisco.com/​en/​US/​products/​ps11389/​products_​implementation_​design_​guides_​list.html.

Installation and configuration worksheet

Make one copy of this worksheet for every node or server in the cluster. Record the network, password, and other information that the installation and setup wizard prompts you to enter for each server. You may not need to record all the information; record only the information that is pertinent to your system and network configuration.

Store the completed worksheets in a secure location for future reference.

Table 1 Cisco MediaSense Installation and Configuration Worksheet

Installation Data

Your Entry

Notes

Platform administrator information

Username:

Password:

Information used to sign in to the Unified Communications Operating System Administration and Cisco Unified Serviceability.

Cisco MediaSense application administrator information

Username:

Password:

Information used to sign in to the Cisco MediaSense Administration and Cisco MediaSense Serviceability.

You can change the entry after installation by using the following CLI commands:

utils reset_application_ui_administrator_name

utils reset_application_ui_administrator_password

Cisco MediaSense cluster deployment information

Primary server IP address:

Secondary server IP address:

Expansion server IP address:

 

The MTU size in bytes for your network.

This setting must be the same on all servers in a cluster.

MTU size:

If you are unsure of the MTU setting for your network, use the default value of 1500 bytes.

Network Interface Card (NIC). This parameter appears only when you choose not to use Automatic Negotiation. Speed is one of :
  • 10 megabits per second
  • 100 megabits per second
  • 1 gigabit per second.

NIC Speed:

Check with your network administrator for further guidance on this setting.

Caution    NIC speeds less than 1 gigabit per second can reduce performance under heavy loads.

Static Network Configuration

IP Address:

IP Mask:

Gateway:

 

DNS Client Configuration

Primary DNS:

Secondary DNS (optional):

Domain:

Provide this information when using hostnames for cluster configuration.

A server hostname cannot be changed after installation.

If you enable DNS, you must configure both forward and reverse lookup information.

Network Time Protocol (NTP) or Hardware Clock configuration for the first server.

Set the NTP for other servers in the Cisco MediaSense deployment to the time on the first server.

Hostname or IP address of the NTP server.

You must specify at least one valid and reachable NTP server. Three NTP server details are preferred.

Enter the same security password for all servers in the Cisco MediaSense deployment.

Security password

The security password must contain at least six alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character.

You can change the entry after installation by using the following CLI command: set password security.

Answer files for unattended fresh installations

You can perform an unattended, fresh installation of Cisco MediaSense by using a platform configuration file called an answer file. Answer files are created using a Web-based application called the Cisco Unified Communications Answer File Generator.

The Answer File Generator simultaneously validates the syntax of your data entries, saves the data, and generates the platform configuration file.

Use an answer file to create and mount a virtual floppy image of MediaSense on a memory stick or a disk. Use this image to perform an unattended installation on the primary node, secondary node, or any expansion nodes in a cluster. You cannot use it to upgrade an installation.

To create an answer file, visit the answer file generation Web site.

For more information, see How to Use the AFG with the Virtual Floppy Drive.

Navigate the installation wizard


Note


If you leave an installation unattended, your monitor screen may go blank. If the screen goes blank:
  • Press Escape to redisplay the current screen and continue the installation.
  • Do not press the Space bar. Pressing the Space bar selects the default option from the current screen and moves you to the next screen.

The following table describes the actions the system takes when you enter certain keys during installation.

To do this...

Press this...

Move to the next field

Tab

Move to the previous field

Alt-Tab

Choose an option

Spacebar or Enter

Scroll up or down in a list

Up and Down arrow

Return to the previous window

Space bar or Enter to choose Back (when available)

Get help for a window

Space bar or Enter

Installation process

The installation process deploys the MediaSense application and the Unified Communications Operating System (Unified OS) from the provided media on the DVD disc.

Before you install the MediaSense, you must address all virtual machine (VM) requirements.

Cisco assumes that you know the VMware toolset and have done the following tasks:

  • Mounted and mapped the DVD drive to the VM host DVD device (physical DVD drive with the DVD disk inserted) or you have mounted your DVD drive to the datastore ISO file.
  • Powered on your VM server in preparation for this installation.
  • Met all of the VM requirements listed in the Unified Communications Virtualization website at http:/​/​cisco.com/​go/​uc-virtualized.

You can install MediaSense from the installation disc and configure it with one DVD insertion. The disc contains the Unified Communications Operating System (Unified OS) and the MediaSense installer. When you run this installer, you install Unified OS and MediaSense at the same time.

Installing MediaSense is a two-step process:

  1. Install MediaSense and Unified OS
  2. Setup the primary server

Note


Before you install any secondary or expansion servers, the primary server must be running and it must be configured with information about the secondary and expansion servers.

Install Cisco MediaSense and Unified OS

Before you begin to install Cisco MediaSense and Unified OS, do the following:

  • Use one of the supported VM template options to plan your full configuration. If your plan does not match one of the supported VM template options, Cisco MediaSense defaults to unsupported mode and a limited number of recording resources become available. Cisco provides no technical support for systems running in an unsupported mode. To view all VM requirements, visit the Unified Communications Virtualization website at http:/​/​cisco.com/​go/​uc-virtualized.
  • Assign the primary and secondary servers. The installation process for the primary server differs from the process for all other servers. After you assign your primary and secondary servers, you cannot change the assignment.
  • Place the CD/DVD device at the top of the BIOS boot order.
  • If you plan to perform an unattended installation, provide a configuration file on a Virtual Floppy Image.

Caution


The installation may fail if an invalid or incorrect IP address was entered when the MediaSense node was added to the Unified CM cluster. Refer to http:/​/​docwiki.cisco.com/​wiki/​Troubleshooting_​Tips_​for_​Cisco_​MediaSense for information on correcting the IP address before restarting the installation.



Caution


If a critical error occurs during installation, the installer prompts you to collect log files. To do this, insert a USB memory key in any available USB port and follow the instructions on the screen. You may need to restart the installation of this node. For more detailed instructions, see How to Dump Install Logs to the Serial Port of the Virtual Machine at cisco.com.


Procedure
    Step 1   If you have a configuration file for an unattended installation, confirm that it is on a Virtual Floppy Image, that the image is on the datastore, and that it is mounted.
    Step 2   Insert the Cisco MediaSense installation disc into the DVD tray and restart the server so that it boots from the DVD. After the server completes the boot sequence, the DVD Found window is displayed.
    Step 3   You are prompted to perform a media check. The media check verifies the integrity of the installation disc. If your disc passed the media check previously, you omit this step.

    To perform a media check, select Yes. To omit the media check, select No.

    1. If you choose to perform the media check, the Media Check Result window displays a progress bar. Depending on your server setup, the media check can take about five minutes to complete.
    2. If the Media Check Result displays PASS, click OK to continue.

      If the media check fails, eject the DVD to end the installation. At this point, the next step depends on your service-level agreement. You can:

      • Obtain another installation disc directly from Cisco Systems.
      • Contact your service provider for assistance.
    Step 4   The system installer checks the hardware to ensure that your system is correctly configured. If the installer makes any changes to your hardware configuration settings, you will be prompted to restart your system.
    1. First, the installer checks for the correct drivers. You may see the following warning:

      No hard drives have been found. You probably need to manually choose device drivers for install to succeed. Would you like to select drivers now?

      To continue the installation, choose Yes.

    2. The installer next checks to see if you have a supported hardware platform. If your server does not meet hardware requirements, the installation process fails with a critical error. If you think the error is not correct, capture the error and report it to your service provider.
    3. Next, the installer verifies the RAID configuration and BIOS settings.

      If the installer must install a BIOS or RAID update, a notification informs you that the system must reboot. Press any key to continue with the installation.

    When the hardware check is complete, the Product Deployment Selection screen is displayed.

    Step 5   The Cisco Unified Communications Product Deployment Selection screen states that Cisco MediaSense will be installed. Click OK to proceed.

    The installation begins.

    Step 6   Select Yes if you agree with the information that is displayed in the Proceed with Install screen. If you select No, the installation is cancelled.

    The Proceed with Install screen displays any pre-existing version of MediaSense on the hard drive and the version that is available on the disc. For a first installation of Cisco MediaSense, the version on the hard drive is displayed as NONE.

    If you plan to perform an unattended installation and provided a configuration information on a Virtual Floppy Drive at Step 1 of this procedure, you now select Yes in the Proceed with install screen. The installer asks no more questions unless there is a discrepancy in the configuration information. After the installation finishes, perform the tasks in Post-installation tasks.

    If you did not provide the configuration information on a Virtual Floppy Image in Step 1, and you select Yes in the Proceed with Install screen, the installation continues with the next step.

    Step 7   In the Platform Installation Wizard screen, select Proceed.

    The software installation begins.

    Note   

    During the reboot, some System Reboot Messages prompt you to press a key. Do not press a key.

    Step 8   During the reboot, the VM prompts you to eject the DVD. Eject the DVD and close the tray.
    Step 9   In the Basic Install screen, click Continue .

    The Basic Install screen launches the Setup Configuration wizard—a series of screens with options pertinent to your MediaSense deployment.

    Step 10   In the Time Zone Configuration screen, use the Up and Down arrow to select the time zone that is the closest match to your server location. Click OK.
    Caution   

    Setting the time zone incorrectly can adversely affect system operation.

    Step 11   In the MTU Configuration screen, select No to keep the default setting (1500).

    The MTU is the largest packet (in bytes) that this host will transmit on the network. Use the default setting if you are unsure of the MTU setting for your network. If you do not want to use the default setting, contact your network administrator for the setting that is required for your deployment.

    Caution   

    If you do not configure the MTU size correctly, network performance can be degraded.

    Step 12   In the Static Network Configuration screen, enter the values for IP Address, IP Mask, and Gateway (GW) Address. Click OK.
    Step 13   In the DNS Client Configuration screen, select Yes.
    Note   
    • If you enable DNS, you can use hostnames to configure the nodes. Hostnames cannot be changed after installation completes.
    • If you disable DNS, you must use IP addresses to configure the nodes.

    If you enable DNS, you must provide values for the Primary DNS and the Domain. Optional values include the Secondary DNS.

    Note   

    If you enable DNS, you must also configure both forward and reverse lookup information in your DNS server. If you do not configure this information, the installation fails on the network check.

    Caution   

    To display both IP addresses, you must configure the Domain Name Server (DNS) suffix information (for the required servers in the cluster) in the server in which Cisco MediaSense is installed. If you plan to install the Cisco MediaSense software without DNS information, make sure you provide only the IP Address as a reference instead of hostnames in all servers in this Cisco MediaSense cluster. See the Command Line Interface Reference Guide for Cisco Unified Communications Solutions at https:/​/​www.cisco.com/​en/​US/​products/​sw/​voicesw/​ps556/​prod_​maintenance_​guides_​list.html for more information.

    Step 14   In the Administrator Login Configuration screen, enter the Administrator ID for the Unified OS (platform) administrator for this deployment. Also enter and confirm the password for this administrator. Select OK.
    Step 15   In the Certificate Information screen, enter values for Organization, Unit, Location, State, and Country. Click OK.
    Step 16   If you are configuring the first server for this MediaSense deployment, select Yes in the First Node Configuration screen. Continue to the next step.

    If you are configuring a secondary server or an expansion server, select No. Go to Step 20.

    Step 17   In the Complete the Network Time Protocol Client Configuration screen, click OK.

    The first server in a Cisco MediaSense deployment can get its time from any external Network Time Protocol (NTP) server that you define. NTP or Hardware Clock configuration is only set for the first node. Other servers in the cluster automatically synchronize their time to the time on the first server.

    Note    You must specify at least one valid and reachable NTP server. Cisco recommends that you configure three NTP servers.
    Step 18   If you are configuring the first server, enter the security password in the Security Configuration screen.
    The security password:
    • Must start with an alphanumeric character and be at least six characters long. It can contain alphanumeric characters, hyphens, and underscores.
    • Must be identical for all servers because the servers use it to authorize communications between them.
    • Must be recorded and kept to use again when you add a secondary server or an expansion server.
    • Can be changed later using the CLI command set password security.

    Select OK.

    Step 19   In the Application User Configuration screen, enter the user ID for the application user. Enter and confirm the password. Click OK.

    This application user is different from the Cisco MediaSense application administrator. To continue the installation the first server, go to Step 22.

    Step 20   If you are not configuring the first server in your deployment, a warning asks you to first configure details for the subsequent server in the Add Server screen. After this configuration is complete, click OK.

    For information, see Server Configuration.

    if you are configuring any subsequent servers in your deployment, the Network Connectivity Test Configuration screen appears.

    Step 21   In the Network Connectivity Test Configuration screen, click No, for the installation to proceed with the network test. You are warned about the first node configuration requirements. Click OK to proceed.

    If you click Yes, then the installation is paused. You can resume the installation after you add the subsequent server information to the primary server. For instructions, see Server Configuration.

    Step 22   In the First-Node Access Configuration screen, add the Host Name and IP Address of the first server. The Security Password is the same as the security password you entered for the first server. Click OK to continue with the installation.

    The Platform Configuration Confirmation screen is displayed.

    Step 23   In the Platform Configuration Confirmation screen, select OK to proceed with the installation.

    The installation process continues. The process may take several hours to complete. Completion time depends on the configuration setup, hardware setup, disk size, and other factors.

    Cisco MediaSense restarts automatically after the installation completes. A login screen displays a successful installation message and a login prompt.


    What to Do Next

    Un-mount the DVD drive mapped to the VM host DVD device (physical DVD drive with the DVD disk inserted) or the DVD drive mounted to the datastore ISO file.

    Proceed with post-installation tasks to complete the set up for every node in the cluster.

    Post-installation tasks

    After installing Cisco MediaSense on your server, you must set some configuration parameters and perform other post-installation tasks before you start using the system.
    Procedure
      Step 1   Upgrade the VM tools.

      For more information on upgrading VM tools, see http:/​/​docwiki.cisco.com/​wiki/​VMware_​Tools.

      Step 2   Setup the primary server.

      See Complete setup for primary server.

      Step 3   Add subsequent servers.

      See Server Configuration.

      Step 4   Setup subsequent servers.

      See Finish setup for subsequent servers.


      Complete setup for primary server

      The MediaSense deployment model is transparent to the MediaSense installer because clustering is performed through the MediaSense Administration interface using the MediaSense Post-Installation Setup wizard.

      Which post-installation setup procedure you perform depends on the answers to the following questions:


      Caution


      After you install the primary server you cannot change your primary server assignment for this deployment.

      For all other information that you specify during the setup procedure, you can use the MediaSense Administration interface to update it or make changes.

      To complete the setup for the primary server in any MediaSense deployment, follow this procedure.

      Procedure
        Step 1   After you complete the installation procedure, the system automatically restarts and then you must sign in to MediaSense Administration for the primary server.

        After you sign in, the Welcome screen of the MediaSense First Server Setup wizard is displayed.

        Step 2   When you are ready to proceed, click Next.

        The Service Activation screen is displayed.

        Step 3   The system internally verifies the IP address of this server and automatically begins enabling the MediaSense feature services in this server. Wait until all the features services are enabled in the Service Activation window. After all the services are successfully enabled, click Next.

        If a feature services cannot be enabled, an error message is displayed in the Status section.

        Table 2 Feature Service Status Description

        Status

        Description

        Take the Following Action

        Enabling

        This service is in the process of being enabled.

        Do nothing. Wait for the state to moved to the Enabled state.

        Enabled

        This service is now fully turned on and ready to function as designed.

        Wait until all the feature services for this server reach the Enabled state. The primary server requires all feature services to be enabled.

        Error

        The system cannot enable this service due to an error.

        Warning   

        If the Database Service or the feature services are not enabled, the system will not allow you to proceed with the setup procedure.

        You response depends on the service that failed to be enabled.

        • If it is Database Service or the Configuration Service, you must first correct the error and re-sign in to restart the initial setup.
        • If it is any other service, you can continue with the setup and fix the errors after the setup is completed. Be aware that your system will not be in full service until you fix these issues.

        After you click Next, the AXL Service Provider screen appears.

        Step 4   In the MediaSense AXL Service Provider screen, enter the AXL Service Provider (IP address), AXL Administrator username, and Password in the respective fields for the Unified CM that should communicate with Cisco MediaSense.

        The Administrative XML Layer (AXL) authentication allows you to enter the Unified CM cluster and retrieve the list of Unified CM servers within that cluster. During the AXL authentication, if the Unified CM Publisher is offline or not available, you can provide the next available Unified CM Subscriber for the AXL authentication.

        The AXL Administrator username may not be same as the Unified CM Administrator username for that cluster. Be sure to add the username for the AXL Administrator to the Standard Unified CM Administrators group and "Standard AXL API Access" roles in Unified CM.

        Note   

        You will not be able to change the password for the AXL user in the Cisco MediaSense application. The Cisco MediaSense application only authenticates the password configured in Unified CM. You can, however, modify the AXL server IP address. See Select AXL service providers.

        If the selected AXL services cannot be enabled, an error message instructs you to reselect AXL service providers.

        After the system accepts the AXL server and user information, the Call Control Service Provider screen appears.

        Step 5   If the client applications using MediaSense need to make outbound recording calls, provide the Unified CM IP address for the Call Control service (referred to as SIP trunk in the Unified CM user interface and documentation) on the MediaSense Call Control Service Provider screen.
        Note   

        Provide this information only if you know the applications using MediaSense. You can get this information by sending an AXL request to the Unified CM server that was configured as the AXL Service Provider.

        Even if it is already enabled, the Call Control Service will not be In service (either directly through Unified CM or from MediaSense using AXL) until the Unified CM information is configured.

        Configure the Unified CM IP Address for Call Control Service (SIP trunk), Route Group, Route List, Recording Profile, and the Route Pattern to ensure that the MediaSense Call Control Service will be In service.

        Step 6   Click Finish to complete the initial setup for the primary server.

        The MediaSense Setup Summary window displays the result of the initial setup.

        When you finish the post-installation process for any MediaSense server, you must access the Unified CM server for your deployment (based on the information provided during the installation and post-installation process). In Unified CM Administration, you will need to configure the SIP Trunk, Route Group, Route List, and Recording Profile. If you do not need to access this URL, you are automatically presented with the MediaSense authentication window when the MediaSense application restarts.

        You have now completed the initial setup of the primary server for MediaSense.

        Sign in to the MediaSense Administration web interface to configure and manage the MediaSense system.


        Details for secondary and expansion servers

        Before you can install Cisco MediaSense on a secondary server or an expansion server, you must go to the primary server and configure details for these servers. You configure details for these servers using the Cisco MediaSense Administration user interface.

        After you go to the primary server and configure details for the secondary server or expansion server, you must install the secondary server or expansion server to complete the clustering process.

        Server Configuration

        For more information, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions on www.cisco.com.

        Procedure
          Step 1   From the Cisco MediaSense Administration menu, select System > MediaSense Server Configuration.
          Step 2   In the MediaSense Server Configuration screen, click Add MediaSense Server.

          The Add MediaSense Server screen in the primary node opens.

          Step 3   If your installation uses DNS suffixes, enter the hostname of the server that you want to add.
          Step 4   If your installation does not use DNS suffixes, enter the IP address of the server that you want to add.
          Step 5   (Optional) Enter the description of the server that you want to add.
          Step 6   (Optional) Enter the MAC address of the server that you want to add.
          Step 7   Click Save.
          Step 8   Click Back to MediaSense Server List.

          MediaSense displays a confirmation message. You see the configuration details of the server that you added in the MediaSense Server List.


          Subsequent server post-installation process

          Before you complete the post-installations for the subsequent servers, be sure that you have already installed Cisco MediaSense on each server and that you have completed the following tasks on each server:

          1. You have completed the setup of the primary server. See Complete setup for primary server. At the minimum, the primary server must be up and functioning with network services before any subsequent server is installed.
          2. You have added the subsequent server details to the primary server. See Server Configuration.
          3. You have defined the User ID and password for the Cisco Unified Communications platform administrator.
          4. You have entered the Network Configuration information for the server. This is a Unified OS requirement.
          5. You have verified that the server for which you want to complete the post-installation process is not the primary server or first node in the cluster. This is a Unified OS requirement.
          6. You have provided the primary server information of the Cisco MediaSense cluster to which this server must join.
          Finish setup for subsequent servers

          The MediaSense deployment model is transparent to the MediaSense installer because the clustering for MediaSense is performed through the MediaSense Administration interface using the MediaSense Post-Installation Setup wizard.

          The post-installation setup procedure that you perform depends on the answers to the following questions:

          • Do you have access to Unified CM? Access is required to continue with the MediaSense installation. Do you have the Unified CM IP address, AXL Admin username, and AXL Admin Password to continue with the post-installation tasks?
          • Did you review the post-installation considerations for the required deployment?

          Caution


          After you complete the initial setup procedure for the secondary server, you cannot change your secondary server assignment for this deployment.

          Use the MediaSense Administration interface to make changes to the information that you specify during the setup procedure. For more information, see Administer and Configure MediaSense.

          Procedure
            Step 1   After you complete the installation procedure specified in Install Cisco MediaSense and Unified OS, the system restarts automatically and you must sign in to MediaSense Administration to install subsequent servers.

            When you sign in, the Welcome screen of the MediaSense Subsequent Server Setup wizard appears.

            Step 2   When you are ready to proceed, click Next.

            You determine the type of server in this Welcome screen. You must decide whether this subsequent server becomes the secondary server or an expansion server. Based on your choice, the list of services to be turned on is displayed on the service activation page.

            • Secondary server: If you enable all of the services in the Service Activation window, this server becomes the secondary server. After you have enabled all the services and the initial setup completes, you cannot change the secondary server assignment. Once a secondary server has been selected, any additional servers will automatically be designated as expansion servers.
            • Expansion servers:The API Service and the Configuration Service are not available on expansion servers. Only the Media Service, Call Control Service, and SM Agent are enabled on expansion servers. A server which has only these last three services enabled becomes an expansion server.

            The following table shows which features can be enabled in each type of server:

            Feature

            Enabled in Primary Server?

            Enabled in Secondary Server?

            Enabled in Each Expansion Server?

            Database Service

            Yes

            Yes

            No

            Configuration Service

            Yes

            Yes

            No

            API Service

            Yes

            Yes

            No

            Media Service

            Yes

            Yes

            Yes

            Call Control Service

            Yes

            Yes

            Yes

            SM Agent

            Yes

            Yes

            Yes

            Select the server type and click Next. The Service Activation screen is displayed.

            Step 3   After the services are enabled, click Finish to complete the initial setup for the subsequent server.

            If a feature service cannot be enabled, an error message is displayed in the Status section.

            The MediaSense Setup Summary window displays the result of the initial setup and MediaSense restarts.

            You have now completed the initial setup of the subsequent server. This subsequent server is ready to record.


            System verification

            After you install Cisco MediaSense, use the following indicators to verify the health of your Cisco MediaSense deployment:

            • Sign in to the Cisco MediaSense Administration on each server. See Access Cisco MediaSense Administration.
            • Sign in to the Cisco MediaSense Serviceability Administration on each server. See Access Cisco MediaSense Serviceability.
            • Services described in the Setup Summary are enabled on each server as pages of your Cisco MediaSense Post-Installation Setup wizard. For status descriptions, see the Feature Service Status Description table in Complete setup for primary server.
            • To confirm that database replication is running between the primary server and subsequent servers, issue the run_db_reset_replication command. If replication is not running, this command starts replication setup. If replication is already running, this command restarts the replication setup.

            Upgrade MediaSense

            This section contains information on how to upgrade MediaSense. MediaSense can only be upgraded from one release to the next supported release. If you are running a an earlier release, you may have to upgrade more than once to bring your system up to the current release.

            If an upgrade does not complete, you can rollback to the previous release and begin the upgrade again.


            Note


            A node can take several hours to upgrade depending on the number and size of recordings it holds. Ensure that you are prepared to wait several hours to complete the upgrade.


            Upgrade considerations

            Keep the following points in mind when you consider a Cisco MediaSense upgrade:

            • Full loads: You cannot run a full call load until after you complete the upgrade on all servers in the cluster.
            • Upgrade sequence: When you upgrade a cluster, you must upgrade the primary server first. You can upgrade the remaining nodes one at a time or upgrade them all at the same time.
            • VM Snapshots: Cisco strongly recommends that you take a VM Snapshot of each node before you begin the upgrade. If an error stops the upgrade process, you can restore these VM Snapshots to roll back the nodes to their previous states.
              • You do not need to stop each node to take its VM Snapshot.
              • You must delete the VM Snapshot from each node after the upgrade. Cisco MediaSense should not run on a node with a VM Snapshot for more than a few days.
            • Temporary outages: You experience a temporary server outage while the software is being installed/upgraded. How long this outage lasts on your configuration and the size of the data that is stored in the database.
            • Aborted calls: Nodes in the Cisco MediaSense cluster stop taking new calls and API requests when you begin the upgrade process. If any calls are in progress when you begin the upgrade, recordings of those calls end in a CLOSED_ERROR state. After the upgrade, each node in the cluster resumes accepting calls when it come back online.
            • Release mismatches: At all times, all servers in the cluster must run the same release of Cisco MediaSense. Even during an upgrade, all the nodes which are operating at any given time must be running the same release. No temporary mismatch is permitted on operating nodes.
            • Incomplete upgrades: If you decide to back out of an upgrade before it completes, you must restore the VM snapshots on all nodes to their previous version.
            • No configuration changes during an upgrade: During the upgrade process, do not make any configuration changes to any server. After all nodes have been upgraded and returned to service, you can resume making configuration changes. However, even then, if you need to roll back the upgrade, you will lose these configuration changes.
            • Restarting an upgrade on a subsequent server: If an upgrade on a subsequent server fails, correct the errors which caused the upgrade failure. Verify the network connectivity of the servers in your cluster. Reboot the subsequent server and ensure that its memory and CPU usage are not too high. Upgrade the subsequent server again.
            • Clusters with one or more nodes storing a large number of recorded sessions: If you have stored a large number of recorded sessions on one or more nodes in the cluster and you do not want to keep these stored sessions, you may want to fresh-install to a major release [such as release 9.0(1)] on the cluster rather than to upgrade the cluster to the major release. As a general rule, the upgrade time per node increases by about 90 minutes per 100,000 stored sessions on that node. Doing a fresh-installation on a cluster may be faster than doing an upgrade on the cluster. However, you must consider that you lose the stored sessions when you do a fresh-installation.

            Upgrade Cluster to Release 9.1(1)

            This procedure describes a cluster where one or more individual nodes (servers) are upgraded. To upgrade individual nodes, see Node upgrade procedures.


            Note


            Upgrading to release 9.1(1) requires a mandatory vRAM upgrade from 8 GB to 16 GB, which impacts the normal upgrade procedure. If you are running MediaSense release 8.5(4) or earlier, you must upgrade to release 9.0(1) before you can upgrade to release 9.1(1). Refer to the Cisco MediaSense Installation and Administration Guide for release 9.0(1) at http:/​/​www.cisco.com/​en/​US/​products/​ps11389/​prod_​installation_​guides_​list.html to upgrade to release 9.0(1) before using the procedure in this document to upgrade to release 9.1(1).


            Before you upgrade the cluster, you may want to review some of the following information sources:

            When you upgrade a cluster:

            • You do not need to stop each node to take its VM Snapshot.
            • You can upgrade the expansion nodes one at a time or upgrade them all at the same time.

            Note


            After you begin the upgrade process on a given node, you cannot cancel it using the Cancel button that appears on some screens. The proper way to cancel the upgrade on a particular node is to restore its Virtual Machine snapshot.


            Procedure
              Step 1   Shut down each VM. See Command Line Interface Guide for Cisco Unified Communications Solutions.
              Step 2   Take a VM snapshot of each node, then
              1. update the virtual memory to 16 GB
              2. update the RAM reservation setting to 16 GB
              3. restart the VM for each node.
              Step 3   Upgrade the primary node and wait for it to restart. (See Node upgrade procedures.)
              Step 4   Upgrade any secondary node and wait for it to restart.
              Step 5   Upgrade any expansion nodes and wait for them to restart.
              Step 6   Once the nodes have all been successfully upgraded, delete the VM snapshot on each node.

              Node upgrade procedures

              This section provides procedures for upgrading nodes from local and remote sources.

              Upgrade nodes from a local source


              Note


              Before you begin this procedure, be aware that just copying the .iso file to the DVD in the first step will not work. Most commercial disk burning applications can create ISO image disks.


              Procedure
                Step 1   If you do not have a Cisco-provided upgrade disk, create an upgrade disk by burning the upgrade file that you downloaded onto a DVD as an ISO image.
                Step 2   Insert the new DVD into the disc drive on the local server that is to be upgraded.
                Step 3   Sign in to the web interface for the Cisco Unified Communications Operating System Administration.
                Step 4   Navigate to Software Upgrades > Install/Upgrade.

                The Software Installation/Upgrade window appears.

                Step 5   From the list, choose DVD.
                Step 6   Enter a slash (/) in the Directory field.
                Step 7   Click Next.
                Step 8   Choose the upgrade version that you want to install and click Next.
                Step 9   In the next window, monitor the progress of the download.
                Cisco MediaSense automatically:
                • Upgrades to the release specified.
                • Switches versions and reboots.
                • Starts taking calls.

                Upgrade nodes from remote sources

                Cisco allows you to use any SFTP server product but certifies certain SFTP products through the Cisco Developer Network (CDN).

                CDN partners, such as GlobalSCAPE, certify their products with specified versions of Cisco Unified Communications Manager. See GlobalSCAPE (http:/​/​www.globalscape.com/​gsftps/​cisco.aspx) for more information.

                Cisco does not support using the free FTDP SFTP product. This is because of the 1GB file size limit on this product. For issues with third-party products which have not been certified through the CDN process, contact the corresponding third-party vendor for support.

                Cisco uses the following servers for internal testing. You may use one of these servers, but you must contact the vendor directly for support:

                You can upgrade nodes from a remote source using one of two methods:

                Upgrade nodes using Unified OS Administration
                Procedure
                  Step 1   Put the upgrade file on an FTP server or SFTP server that the node that you are upgrading can access.
                  Step 2   Sign in to the web interface for Unified OS Administration.
                  Step 3   Navigate to Software Upgrades > Install/Upgrade. The Software Installation/Upgrade window is displayed.
                  Step 4   From the list, choose Remote Filesystem.
                  Step 5   In the Directory field, enter the path to the directory that contains the patch file on the remote system. If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path.

                  For example, if the upgrade file is in the patches directory, enter /patches

                  If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including the following:

                  • Begin the path with a forward slash (/) and use forward slashes throughout the path.
                  • The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute path (for example, C:).
                  Step 6   In the Server field, enter the server name or IP.
                  Step 7   In the User Name field, enter your user name on the remote server.
                  Step 8   In the User Password field, enter your password on the remote server.
                  Step 9   Select the transfer protocol from the Transfer Protocol field.
                  Step 10   To continue the upgrade process, click Next.

                  The option to "Switch to new version after upgrade" may be safely ignored.

                  Step 11   Choose the upgrade version that you want to install and click Next.
                  Note   

                  If you lose your connection with the server or close your browser during the upgrade process, you may see the following message when you try to access the Software Upgrades menu again.

                  Warning    Another session is installing software, click Assume Control to take over the installation. If you are sure you want to take over the session, click Assume Control. If Assume Control does not display, you can also monitor the upgrade with the Real Time Monitoring Tool.
                  Step 12   In the next window, monitor the progress of the download.
                  Cisco MediaSense automatically:
                  • Upgrades to the release specified.
                  • Switches versions and reboots.
                  • Starts taking calls.

                  Upgrade nodes using CLI

                  Note


                  If you decide not to upgrade from the CLI, you can use the web interface of the Unified OS Administration to upgrade a node from a network location or to upgrade a node from a remote server. For instructions, see Upgrade nodes using Unified OS Administration.
                  Procedure
                    Step 1   Put the upgrade file on an FTP or SFTP server that the server that you are upgrading can access.
                    Step 2   Sign in to the Unified OS console. See CLI access for more information.
                    Step 3   Enter utils system upgrade initiate at the CLI prompt.

                    The following options display in the console:

                    • 1) Remote Filesystem Via SFTP
                    • 2) Remote Filesystem Via FTP
                    • 3) DVD/CD
                    • q) quit
                    Step 4   Enter 1 or 2 to select the remote file system containing your upgrade file.
                    Step 5   Enter the path to the directory that contains the upgrade file on the remote system. If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path.

                    For example, if the upgrade file is in the patches directory, enter /patches

                    If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including the following:

                    • Begin the path with a forward slash (/) and use forward slashes throughout the path
                    • The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute path (for example, C:).
                    Step 6   Enter the server name or IP.
                    Step 7   Enter your user name on the remote server.
                    Step 8   Enter your password on the remote server.
                    Step 9   Enter the SMTP host server or press Enter to continue.
                    Step 10   Select the transfer protocol.
                    Step 11   Choose the upgrade version that you want to install and press Enter.
                    Step 12   Answer Yes to the prompt to start the installation.
                    Step 13   Monitor the progress of the download.
                    Cisco MediaSense automatically:
                    • Upgrades to the release specified.
                    • Switches versions and reboots.
                    • Starts taking calls.

                    Rollback cluster

                    All nodes in aCisco MediaSense cluster must run the same software version. If an upgrade fails, you can restore the VM Snapshots on the nodes to rollback the software to a previous version. After you rollback the software on the nodes in a cluster, you lose all recordings, lose all configuration changes, and lose all metadata changes that were made after the upgrade. You regain all recordings that were deleted after the upgrade. You keep the Refresh Upgrade COP files on each node because you installed these files before you took the VM Snapshots.

                    Cisco MediaSense clusters cannot run a full call load until you complete the final step in this rollback procedure.


                    Note


                    Be sure that you use Cisco MediaSense Serviceability Administration to perform this procedure. Do not use Cisco Unified Serviceability Administration. You can find Cisco MediaSense Serviceability Administration in the Navigation drop-down menu.


                    Procedure
                      Step 1   Stop all nodes in the cluster.
                      Step 2   Restore and delete the VM Snapshots from all nodes in the cluster.
                      Step 3   Using a Web browser, sign into Cisco MediaSense Serviceability Administration.
                      Step 4   Restart the primary node and wait for it to come back into service.
                      Step 5   Sequentially, or at the same time, restart the remaining nodes.

                      After each node comes back into service, it begins taking calls again.


                      Install COP files

                      The Cisco Options Package (COP) file provides a generic method to deploy Cisco software outside the normal upgrade process. You can use a COP file to install new locales, install patch fixes, and install virtualization tools. You must download and save the COP file before you install it on the nodes in a Cisco MediaSense cluster.

                      The procedure for installing a COP file on a node is almost the same as the procedure for upgrading Cisco MediaSense on that node. The only difference in the COP file procedure is that you download a COP file instead of downloading an upgrade (ISO) file.

                      COP files can generally be installed on an active, running system in a shorter time frame than an upgrade file. However, unlike upgrades, COP files cannot be removed or rolled back.

                      The following guidelines apply to installing COP files:

                      • Install the COP file on every node (server) in a Cisco MediaSense cluster.
                      • Restart the node after you install a COP file on it.

                      Note


                      This procedure provides general guidelines for installing COP files. Before you use this procedure, check the Readme file for the specific COP file that you want to install. If the instructions in the Readme file differ from these general guidelines, follow the instructions in the Readme file instead.
                      Procedure
                        Step 1   Go to the Cisco MediaSense Download Software Website at http:/​/​www.cisco.com/​cisco/​software/​type.html?mdfid=283613140&catid=null.
                        Step 2   Download and save the Cisco MediaSense COP file to a local source or to an SFTP server that can be accessed by the Cisco MediaSense server.
                        Step 3   If you downloaded and saved the COP file to a local source, follow the instructions in Upgrade nodes from a local source.
                        Step 4   If you downloaded and saved the file to an SFTP server, follow the instructions in Upgrade nodes from remote sources.
                        Step 5   After you install the COP file on all nodes in the cluster, go to the web interface for Cisco Unified OS Administration. To verify the COP file installation, navigate to Show > Software.

                        The Software Packages window displays the installed Partition Version and the additionally Installed Software Options with its corresponding status.