Installation and Administration Guide for Cisco MediaSense Release 9.0(1)
Cisco MediaSense installation
Downloads: This chapterpdf (PDF - 938.0KB) The complete bookPDF (PDF - 2.07MB) | Feedback

Cisco MediaSense installation

Contents

Cisco MediaSense installation

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, Release 9.0(1) guide at http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html.

Analyze storage requirements

Analyze all storage requirements before installing Cisco MediaSense. You cannot change any storage-related settings after installation. See Media storage requirements.

Supported Deployments

Cisco MediaSense supports the following deployments in this release:

  • One-server deployment: One active server
  • Two-server deployment: Two active servers providing high availability
  • Three-server deployment: Two active servers providing high availability and one expansion server to provide additional recording capacity
  • Four-server deployment: Two active servers providing high availability and two expansion servers to provide additional recording capacity
  • Five-server deployment: Two active servers providing high availability and three expansion servers to provide additional recording capacity

Note


Services Ready Engine (SRE) installations are limited to One-Server and Two-Server deployments.


In all the deployments, the installation configuration for the primary server differs from the installation configurations for other servers in the same deployment. If you are configuring any server in a Cisco MediaSense deployment, be aware that the platform administrator configures the Cisco MediaSense application administrator username and password (in addition to the platform and security password). See Install Cisco MediaSense and Unified OS for further details.


Note


The application administrator username and password must be the same in all servers in a Cisco MediaSense deployment. You can reset the application administrator username and password using the utils reset_application_ui_administrator_name and the utils reset_application_ui_administrator_password CLI commands.

Installation and configuration worksheet

Make one copy of this worksheet for every node or server in the cluster. Use one copy for each server and record the network and password and other information that the installation and setup wizard prompt you to enter. 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_passwo rd

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. Default: 1500 bytes.

Network Interface Card (NIC) speed is either 10 megabits per second, 100 megabits per second, or 1 gigabit per second. This parameter appears only when you choose not to use Automatic Negotiation.

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:

You must provide this information because DHCP is not supported in this release.

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.

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.

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 Cisco MediaSense application and the Unified Communications Operating System (Unified OS) from the provided media on the DVD disc.

Before you install the Cisco 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 Cisco MediaSense from the installation disc and configure it with one DVD insertion. The disc contains the Unified Communications Operating System (Unified OS) and the Cisco MediaSense installer. When you run this installer, you install Unified OS and Cisco MediaSense at the same time.

Installing Cisco MediaSense is a two-step process:

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

Note


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

Install Cisco MediaSense and Unified OS

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

  • 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.
  • Address all VM requirements on the Unified Communications Virtualization website at http://cisco.com/go/uc-virtualized.
  • Use one of the supported VM template options to plan your system configuration. If your configuration 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.
  • Configure at least one media disk on the VM. If no media disk is available, installations fail near the end of the process. Each media disk must be at least 200 GB or larger. Thin provisioning is not supported for any disks.
  • Place the CD/DVD device at the top of the BIOS boot order.
  • If you want to perform an unattended installation, provide a configuration file on a Virtual Floppy Image.
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   To perform a media check, select Yes. To skip the media check, select No.

    The media check verifies the integrity of the installation disc. If your disc passed the media check previously, you can skip this step.

    1. If you choose to perform the media check, the Media Check Result window is displayed with the progress bar for the media check.
      Note   

      Depending on your server setup, the media check can take approximately five minutes to complete.

    2. If the Media Check Result displays PASS, then click OK to continue the installation.

      If the media check fails, eject the DVD to end the installation. At this point you have several choices depending on your service-level agreement:

      • Obtain another installation disc directly from Cisco Systems.
      • Contact your service provider for assistance.
    Step 4   The system installer performs the following hardware checks 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 installation process checks for the correct drivers, and 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 installation 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. The installation process next verifies RAID configuration and BIOS settings.

      If the installation program must install a BIOS or RAID update, a notification appears telling 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 with the Cisco MediaSense installation.

    The installation process 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 Cisco MediaSense on the hard drive (if any) and the version that is available on the disc. For the initial installation of Cisco MediaSense, the version on the hard drive is displayed as NONE.

    To perform an unattended installation, you must have provided pre-existing configuration information on a Virtual Floppy Drive at Step 1 of this procedure. If you provided the configuration information on a Virtual Floppy Drive at Step 1, and 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   Select Proceed in the Platform Installation Wizard screen to set up the initial configuration for the Cisco MediaSense platform.

    If you choose to Skip the initial configuration, you have the option to complete the initial configuration when the OS installation ends.

    The software installation begins.

    Caution   

    If a critical error occurs during installation, you are prompted 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 on collecting log files, see How to Dump Install Logs to the Serial Port of the Virtual Machine at cisco.com.

    Note   

    System Reboot Messages appear during the reboot, some of which prompt you to press a key. Do not press a key.

    Note   

    During the reboot, the VM prompts you to eject the DVD. This is normal. You can retrieve your disc at this point and close the tray.

    Step 8   In the Basic Install screen, click Continue . (This screen appears only for a fresh installation.)

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

    Step 9   Required: 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 affect system operation.

    Step 10   Recommended: 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 configure the MTU size incorrectly, your network performance can be affected.

    Step 11   In the DHCP Configuration screen, select No.
    Note   

    DHCP is not supported in Release 9.0(1).

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

    If you enable DNS in theDNS Client Configuration, you must provide the DNS server values in the DNS Client Configuration screen. Required values include Primary DNS and Domain. Optional values include Secondary DNS.

    Note   

    If you select Yes to enable DNS, you must also configure both forward and reverse lookup information in your DNS server. Furthermore, if you select Yes for DNS, the network configuration will be validated with the DNS and the installation fails on the network check if you do not configure the forward and reverse lookup information.

    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   In the First Node Configuration screen, select Yes if you are configuring the first server for this Cisco MediaSense deployment. 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, then in the Security Configuration screen, enter the security password. Select OK.
    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.
    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 see. After this configuration is complete, click OK.

    For information, see Add new server details in Primary server Administration.

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

    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 Add new server details in Primary server Administration.

    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.

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

    For instructions, see Post-installation tasks.


    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 Add new server details in Primary server Administration.

      Step 4   Setup subsequent servers.

      See Finish setup for subsequent servers.


      Network services

      In the Cisco MediaSense and Unified OS user interfaces, each Cisco MediaSense service name is preceded by the product name. To avoid redundancy in this document, service names are sometimes referred to without the preceding product name.

      Network services are installed automatically. Because these services are required for basic functionality, you cannot enable or disable them in the Service Activation window. After the installation, network services start automatically in each server in the cluster. You can stop the network services if a need arises.

      Network services include the following:

      • Cisco MediaSense Administration: Enables you to configure Cisco MediaSense with a graphical user interface.
      • Cisco MediaSense Serviceability Administration: Enables you to configure the Cisco MediaSense Serviceability application using the graphical user interface.
      • System Service: Enables you to control service operations within Cisco MediaSense clusters. It does not have a separate user interface. Like other network services, the System Service is operational at startup. This service manages the clustering and setup functionality for the secondary server and expansion servers.
      • Perfmon Agent: Enables you to control the performance monitoring infrastructure. It does not have a separate user interface and operates seamlessly within the Cisco MediaSense Serviceability Administration. Like other network services, the Perfmon Agent is operational at startup. The Java Management Extensions (JMX) technology, which allows you to manage and monitor applications and other system objects, is represented by objects called Managed Beans (MBeans). The Perfmon Agent retrieves the counter values from the JMX MBeans and writes it to the Unified CM database.
      • Diagnostics Service: Enables you to troubleshoot and debug Cisco MediaSense. This service is present in all Cisco MediaSense servers. It does not have a separate user interface. Like other network services, the Diagnostics Service is operational at start up.

      Feature services

      All feature services are installed on the primary and secondary nodes (servers) in a cluster. Expansion nodes have only the Media Service, Call Control Service, and SM Agent.

      Cisco MediaSense contains the following feature services:

      • Configuration Service: Saves and updates all changes made to the Cisco MediaSense configuration database. Each multiple-server cluster can have only two instances of the Configuration Service, one instance is in the primary server and the other instance is in the secondary server. If a cluster has more than two servers, the expansion servers cannot have a Configuration Service.
      • API Service: Processes API requests and enables communication between the user interface and the server. You can enable the API Service only after the Database Service is enabled. Each multiple-server cluster can have only two instances of the API Service, one instance is in the primary server and the other instance is in the secondary server. If a cluster has more than two servers, the expansion servers do not have an API Service.
      • Database Service: Contains and controls the meta database and the configuration database. Each multiple-server cluster can only have two instances of the Database Service, one instance is in the primary server and the other instance is in the secondary server. Each server writes data only to its local database. The primary and secondary servers interact to synchronize data.
      • Media Service: Receives, saves, and plays back media. The Media Service must be enabled before the Call Control Service. This service is available in all servers in the cluster.
      • Call Control Service: Coordinates call receiving and recording. The Call Control Service can only be enabled if the Media Service is already enabled. This service is available in all servers in the cluster. The Call Control Service is referred to as the SIP trunk in the Unified CM user interface and Unified CMdocumentation.
      • SM Agent: Monitors the overall storage in each server in the cluster and generates threshold events based on disk usage. This service is available in all servers and should be activated before the Media Service and Call Control Service.

      Cisco MediaSense cluster deployments

      In a Cisco MediaSense deployment, a cluster contains a set of servers, with each server containing a set of services. Cluster architecture provides high availability and failover. If the primary server fails, there is automatic failover to the secondary server. High availability servers must be in the same LAN network. High availability is provided for recording but not for playback.

      Cisco MediaSense functions only within local area networks (LAN). Wide are networks (WAN) are not supported. All Cisco MediaSense servers and Unified CM servers must be located in the same LAN. Within a LAN, the maximum round-trip delay between any two servers must be less than 2 ms.

      The primary and secondary servers in a Cisco MediaSense deployment are synchronized when administrative changes are made on either server. Database replication copies the data automatically from the primary server to the secondary server, and vice versa.

      The following cluster deployment rules are enforced by the installation and configuration procedures:

      • All servers in the same cluster must run the same version of Cisco MediaSense.
      • A Cisco MediaSense deployment can consist of one to five Cisco MediaSense servers. Each server in a Cisco MediaSense cluster must always have a Call Control Service, Media Service, and an SM Agent.
      • Cisco MediaSense supports any of the following combinations of servers:
        • One primary server.
        • One primary server and one expansion server.
        • One primary, one secondary server, and from one to three expansion servers.
      • Cisco MediaSense does not support one primary server and two or more expansion servers.
      • SRE installations are limited to single-server or dual-server deployments.

      Single-server deployments

      A single-server deployment has one Cisco MediaSense server on the Unified Communications OS platform. All network services are enabled by default.

      In single-server deployments, the primary server has the following feature services:
      • API Service
      • Configuration Service
      • Call Control Service
      • Media Service
      • Database Service
      • Storage Management Agent (SM Agent)

      Figure 1. Cisco MediaSense single-server deployment



      Each single-server deployment supports a maximum of 300 simultaneous sessions and a Busy-Hour Call Completion rate (BHCC) of 9000 sessions per hour, with each call having a two-minute average duration. Single-service deployments enable you to add more servers later to address redundancy issues, to provide high availability, to increase storage capacity, and to increase simultaneous recording capacity.

      Dual-server deployments

      A dual-server deployment has two Cisco MediaSense servers on the Unified Communications OS (Unified OS) platform. The first server is called the primary server. The second server is called the secondary server. All network services are enabled by default on both servers

      Both primary and secondary servers have the following feature services:
      • API Service
      • Configuration Service
      • Call Control Service
      • Media Service
      • Database Service
      • Storage Management Agent (SM Agent)
      Figure 2. Dual-server deployment. Dual-server deployments provide high availability. The recording load is automatically balanced across the primary and secondary servers because all services are always active on both servers.




      Note


      Cisco MediaSense does not provide automatic load balancing in the API Service or the Configuration Service. When both of those services are enabled on the primary and secondary servers, you must point your browser or server-based API to one of these services.


      See the Cisco MediaSense Solution Reference 9.0(1) Network Design guide for details about the maximum number of simultaneous recordings, playback, and monitoring sessions that are supported.

      Three-server deployments

      Three-server deployments have a primary server, a secondary server, and one expansion server. All network services are enabled by default on all servers in the cluster.

      The primary server and the secondary server have the following feature services:
      • API Service
      • Configuration Service
      • Call Control Service
      • Media Service
      • Database Service
      • SM Agent
      The expansion server has the following feature services:
      • Call Control Service
      • Media Service
      • SM Agent
      Figure 3. Three-server deployment. The three-server model provides redundancy and increases storage capacity and simultaneous recording and playback capacity. The recording load is automatically balanced across the servers.




      Note


      Cisco MediaSense does not provide automatic load balancing in the API Service and Configuration Service on the primary and secondary servers. While those services are enabled, you must point your browser or server-based API to only one of these services.

      See the Solution Reference Network Design for Cisco MediaSense 9.0(1) for details about the maximum number of simultaneous recording sessions, playback sessions, and monitoring sessions that are supported.

      Four-server and five-server deployments

      Four-server and five-server deployments have one primary server, one secondary server, and two or three expansion servers. This deployment model provides redundancy, increases storage capacity, and increases capacity for simultaneous recording and playback sessions. The recording load is automatically balanced across the servers because services are always active on their respective servers. See the Solution Reference Network Design for Cisco MediaSense Relase 9.0(1) for details about the maximum number of simultaneous recording sessions, playback sessions, and monitoring sessions that this deployment supports.


      Note


      Cisco MediaSense does not provide automatic load balancing in the API Service and Configuration Service on the primary and secondary servers. While those services are enabled, you must point your browser or server-based API to only one of these services.


      All network services are enabled by default on all servers in the cluster.

      Primary servers and secondary servers have the following feature services:
      • API Service
      • Configuration Service
      • Call Control Service
      • Media Service
      • Database Service
      • Storage Management Agent (SM Agent)
      The remaining servers, called expansion servers, only have the following feature services:
      • Call Control Service
      • Media Service
      • Storage Management Agent (SM Agent)
      Figure 4. Five-server deployment



      Cisco MediaSense high availability deployments

      Some deployments require that all available media is recorded. A Call Control Service failure may result in no recordings unless your deployment supports high availability. If Unified CM cannot contact one of the Cisco MediaSense servers, you must ensure that an alternate server is available for Unified CM or CUBE to make the required connection.

      For more information, see the Solution Reference Network Design Guide for Cisco MediaSense Release 9.0(1) at http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html.

      Data replication considerations

      Database high availability support in Cisco MediaSense deployments is provided using Informix Enterprise Replication (ER) for both the Meta database and Config database. While a Cisco MediaSense cluster can have up to five servers, data replication is enabled only between the primary server and secondary server.

      At installation time, if the server you are installing is identified as a secondary server, the following considerations apply to this server:

      • This server will automatically apply the on-tape backup from the primary server without any constraints on the data size in the primary server.
      • Data replication is performed between the primary and secondary servers. So, data written to the primary server is also replicated to the secondary server, and vice versa.

        Caution


        If you are installing a primary server, the preceding considerations do not apply.

      The replication behavior between the primary and secondary Cisco MediaSense servers differs based on the time of replication:

      • Activation time: During the service activation process, Informix ER automatically begins replication between the primary and secondary servers. The differential data between both servers are replicated from the primary server to the secondary server.
      • Run time: During run time, data replication is bidirectional. For any reason, if one of the Cisco MediaSense servers is shut down or in a failed state, data continues to be written to the surviving server. When the shut down or failed server is revived, Informix ER automatically restarts between the two servers and synchronizes the data. Depending on the data size, this synchronizing time may vary. Retention period refers to the number of days for which data can be stored on the surviving server without breaking the replication. See the Cisco MediaSense Solution Reference Network Design guide for details about the database retention period recommendations.

      Data replication and recovery for primary or secondary node

      If either the primary or secondary server goes out of service, the database replication process will proceed as follows:

      If either node goes out of service, MediaSense continues to write data to the recording database. Because the data cannot be replicated to the out of service node, Informix stores the data in the ora_ersb replication buffer on the node that is still working (ersb stands for enterprise replication smart blob). If the node that is out of service comes back up before ora_ersb is full, replication is automatically restored and the data in ora_ersb is synchronized between both nodes.

      If one node is out of service for an extended period, the ora_ersb buffer on the working node may fill up. If ora_ersb reaches 90% of its capacity, the system will automatically tear down (stop) replication on the working node (which will then act like a single node). The system does this to prevent ora_ersb from getting too full. If the system did not tear down replication and ora_ersb reached 99% of its capacity, writing of data would stop on the working node and the system would become dysfunctional.

      If replication is torn down (stopped) on the working node, it will be automatically restored after the out of service node comes back into service. User intervention is not required. After replication is restored, data sync jobs are launched to compare both the meta data and the configuration data on both nodes, and synchronize this data if needed.

      You can check the data sync job status by running the following CLI command on either one of the nodes:

      show db_synchronization status [db_ora_meta|db_ora_config]

      Deployment considerations for high availability

      Follow these guidelines to ensure a highly available deployment and to provide data replication:

      • Verify that the API Service is enabled and running: The API Service monitors its internal performance to provide overload protection. If an overload condition is detected, the API Service may begin to automatically reject third-party requests. Client applications should be able to retry requests on the alternate API Service if they receive rejections.
      • A deployment can contain up to five possible Call Control Services in the cluster. The following table identifies the possible Cisco MediaSense scenarios.
      Table 2 Cisco MediaSense High Availability Scenarios

      Cisco MediaSense Scenarios

      with Unified CM

      with CUBE

      Normal Cisco MediaSense scenario

      The Unified CM uses a round-robin method to reach an available Call Control Service to place an outbound call. Otherwise, it tries to place a call to the next Call Control Service and times out after the last Call Control Service.

      CUBE always sends a call to the first Cisco MediaSense server in the media-recording list.

      Failed Cisco MediaSense scenario

      Unified CM uses the next available Cisco MediaSense server in the list.

      CUBE uses the next available Cisco MediaSense server in the media-recording list.

      Failure condition considerations

      If a Cisco MediaSense primary or secondary server fails for any reason, the surviving server continues to write meta data to the meta database and to the Cisco MediaSense Enterprise Replication Smart Binary Large Object. This large object is referred to as the ora_ersb.

      If ora_ersb reaches 90% of its capacity, replication on the surviving server stops so that the surviving server can continue to write data. If the ora-ersb exceeds its capacity, the system becomes dysfunctional.

      Recovery time is the time taken by the failed Cisco MediaSense server to synchronize data with the surviving server after the failed server comes back in service. The length of recovery time for a failed server depends on the following factors:

      • Volume of data written to the surviving server when one server is down
      • Duplex network connection speed between the two servers
      • Level of call load running if and when recovery is in progress
      • Whether replication stopped on the surviving server

      A failed Cisco MediaSense system can degrade at two levels:

      • The ora_ersb is less than 90% full: If the failed server is brought back before the ora_ersb is 90% full on the surviving server, no metadata is lost.
      • The ora_ersb is more than 90% full: If the ora_ersb becomes 90% full on the surviving server before the failed server is restored, replication stops on the surviving server. This allows the surviving server to continue to write data, so no metadata is lost. When the failed server comes back into service, replication must be re-established and it may take longer for services to be ready. Because replication was stopped, it may take substantially longer to synchronize the data after the failed server comes back into service.

      In both situations, when the failed server is back up and available, replication automatically starts to catch up. No manual intervention is needed. You do not need to issue the run_db_reset_replication command after the server comes up.

      For details about failure recovery times, see the Solution Reference Network Design for Cisco MediaSense Release 9.0(1) guide at http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html).

      Primary server post-installation process

      When you installed Cisco MediaSense as a primary server, you should have already completed the following tasks during the process:

      1. Entered the Network Configuration information for the machine (Unified OS requirement).
      2. Identified this server as the First Node (Unified OS requirement).
      3. Configured the User ID and password for the Cisco Unified Communications platform administrator and the Cisco MediaSense application administrator.
      4. After you complete the installation process and the system restarts, you see the Cisco MediaSense First Server Setup Wizard.

      Complete setup for primary server

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

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


      Caution


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

      If you later need to update all other information that you specify during the setup procedure, you can use the Cisco MediaSense Administration interface to make changes.

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

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

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

        Step 2   Read the message in this screen and 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 Cisco 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 3 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   (Optional) On the MediaSense Call Control Service Provider screen, you need to provide the Unified CM IP address for the Call Control service (referred to as SIP trunk in the Unified CM user interface and documentation). Provide this information only if you know the applications using Cisco MediaSense (for example, if the client applications need to make outbound recording calls).
        Note   

        You can get this information by sending an AXL request to the Unified CM server that was configured as the AXL Service Provider.

        If you choose to skip this step, you can add the information later.

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

        If you enter the information in this screen, you will need to 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 Cisco 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 Cisco 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 Cisco MediaSense authentication window when the Cisco MediaSense application restarts.

        You have now completed the initial setup of the primary server for Cisco MediaSense. You must sign in to the Cisco MediaSense Administration web interface before you configure and manage the Cisco MediaSense system.

        Note   

        Effective Release 8.5(4), the user does not select the recording mode (pruning policy for recordings) in the post-installation wizard. The default behavior after installation is for MediaSense to automatically prune recordings older than 60 days and when disk space for new recordings is required. For Release 8.5(4) and later, the pruning policy for recordings can be configured (and subsequently changed) after installation is complete, by using the options in the MediaSense administration pages.


        Information for subsequent servers

        Before you install Cisco MediaSense on the second server, you must first add the new server details to the primary server using the Cisco MediaSense Administration interface.

        After you add the new server details in the primary server of the cluster, you must install the server to complete the clustering process.

        Add new server details in Primary server Administration

        To add the new server details to an existing Cisco MediaSense cluster, follow this procedure.

        Procedure
          Step 1   From the Cisco MediaSense Administration user interface of the primary Cisco MediaSense server, select System > MediaSense Server Configuration.

          The MediaSense Server Configuration web page is displayed.

          Step 2   In the MediaSense Server Configuration web page, you can view servers or add servers to that Cisco MediaSense cluster.

          The Server Configuration window is displayed. It lists all configured servers in this cluster. The primary server cannot be changed or configured.

          See Cisco MediaSense cluster deployments for more information about clusters. You cannot assign the server type in this web page. You can assign the server type only during the post-installation procedure. See Finish setup for subsequent servers. Between the time that a new server is added to the MediaSense Server list and until the time that its post-installation is successfully completed, the type for the new server remains unknown.

          Step 3   In the MediaSense Server Configuration web page, click Add MediaSense Server.

          The Add MediaSense Server web page is displayed.

          Step 4   Enter the IP address and hostname for the new server. All other fields in this page are optional.
          Caution   

          The IP address information is displayed only if you configure the Domain Name Server (DNS) suffix information for each required Cisco MediaSense server in the cluster. If you plan to install Cisco MediaSense without DNS information, provide only the IP address as a reference instead of using the host names in all servers in the cluster.

          Note    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 5   Click Save to add and save the details of the new server.

          The Cisco MediaSense database is updated and saved.

          Click Reset, to have all settings revert to the previously configured list of servers without making any changes.

          Click Back to MediaSense Server List to return to the MediaSense Server List page at any time.


          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 Add new server details in Primary server Administration.
          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 Cisco MediaSense deployment model is transparent to the Cisco MediaSense installer because the clustering for Cisco MediaSense is performed through the Cisco MediaSense Administration interface using the Cisco 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 Cisco 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.

          If you later need to update information that you specify during the setup procedure, you can use Cisco MediaSense Administration interface to make changes. For more information, see Cisco MediaSense Administration.

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

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

            Step 2   Read the message in this screen and 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 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.
            • Expansion servers: If both the API Service and the Configuration Service have been activated in the secondary server, these services are no longer available. Only the Media Service, Call Control Service, and SM Agent remain available for activation. 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. Cisco 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 Administration.
            • 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.

            Upgrades and rollbacks

            You can upgrade Cisco MediaSense Release 8.5(4) to Release 9.0(1). If you are running a previous release, you must upgrade to Cisco MediaSense Release 8.5(4) before you can upgrade to Release 9.0(1).

            If an upgrade to Release 9.0(1) does not complete, you can rollback to Release 8.5(4) and begin the upgrade again.

            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 Release 9.0(1) on the cluster rather than to upgrade the cluster to Release 9.0(1). 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 consider that you lose the stored sessions when you do a fresh-installation.

            Upgrade cluster from Release 8.5(4) to Release 9.0(1)

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

            If you are running Cisco MediaSense Release 8.5(3) or earlier, you must upgrade to Cisco MediaSense Release 8.5(4) before you can upgrade to Cisco MediaSense Release 9.0(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   Install the Refresh Upgrade COP file on each node.
              Step 2   Take a VM snapshot of each node.
              Step 3   Upgrade the primary node and wait for it to restart.
              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   Update the VM settings and 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 Source 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 Release 9.0(1).
                • 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 Source 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, which starts with a drive letter (for example, C:).address.
                  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 Release 9.0(1).
                  • 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   Issue the utils system upgrade initiate command at the CLI prompt.

                    The following source list 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 denote Remote Filesystem.
                    Step 5   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, which starts with a drive letter (for example, C:).address.
                    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   Select the transfer protocol.
                    Step 10   Choose the upgrade version that you want to install and press Enter.
                    Step 11   Monitor the progress of the download.
                    Cisco MediaSense automatically:
                    • Upgrades to Release 9.0(1).
                    • Switches versions and reboots.
                    • Starts taking calls.

                    Update VM Settings and Delete VM Snapshot

                    After you are satisfied that the cluster upgrade was successful, perform the following steps on each node in the cluster to finalize the virtual machine settings.

                    Procedure
                      Step 1   Shut down the virtual machine.
                      Step 2   Delete the VM snapshot that was taken at the start of the upgrade process.
                      Step 3   Modify the VM settings as follows:

                      For Primary and Secondary nodes, set

                      • Guest Operating System to Red Hat Enterprise Linux 5 (32-bit).
                      • Number of CPUs to 7.
                      • CPU Resource Reservation to 15000 MHz.

                      For Expansion nodes, set

                      • Guest Operating System to Red Hat Enterprise Linux 5 (32-bit).
                      • Number of CPUs to 5.
                      • CPU Resource Reservation to 10000 MHz.

                      For SRE nodes, set

                      • Guest Operating System to Red Hat Enterprise Linux 5 (32-bit).
                      • Number of CPUs to 2.
                      • CPU Resource Reservation to 2200 MHz.
                      • Memory Resource Reservation to 5460 MB.
                      Step 4   Restart the virtual machine.

                      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.

                      When you rollback from Cisco MediaSense Release 9.0(1), you can safely run Cisco MediaSense Release 8.5(4) with the COP file installed.

                      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.


                          Server IP Address changes

                          You may want to change the IP address of a Cisco MediaSense server for a several reasons, such as moving the server from one segment to another or resolving a duplicate IP address problem.

                          Effective Cisco MediaSense Release 8.5(3), you can change the IP address of any server in a Cisco MediaSense cluster using one or more of the Set Network CLI commands. See Set network commands.

                          Prepare system for IP Address change

                          Perform the following tasks to ensure that your system is prepared for a successful IP Address change.

                          Procedure
                            Step 1   List all servers in the cluster and note whether the servers are defined by using IP Addresses or byhostnames.
                            • If you are verifying the list from the Cisco MediaSense Administration interface on the primary server, navigate to System > MediaSense Server Configuration. A list of all servers in the cluster is displayed.
                            • If you are verifying the list from the CLI on the primary server, issue the Show Network Cluster command.
                            1. Capture the details of this list for later reference.
                            Step 2   Save a list of the hostname and IP address of each server in the cluster.
                            Step 3   Ensure that all servers in the cluster are running and available by checking for any active ServerDown alerts.

                            You can check from the Unified RTMT interface or from the CLI on the primary server.

                            • To check from the Unified RTMT interface, access Alert Central and check for ServerDown alerts.
                            • To check from the CLI on the primary server, issue the file search activelog syslog/CiscoSyslog ServerDown command and inspect the application event log.
                            Step 4   Check the database replication status on all Cisco MediaSense servers in the cluster to ensure that all servers are replicating database changes successfully.

                            You can check by using the Unified RTMT interface or a CLI command.

                            • Unified RTMT interface: Access the Database Summary and inspect the replication status.
                            • CLI: Enter the command shown in the following example:
                              show perf query class "Number of Replicates Created and State of Replication"
                              ==>query class:
                              - Perf class (Number of Replicates Created and State of Replication)
                              has instances and values:
                              ReplicateCount  -> Number of Replicates Created   = 344
                              ReplicateCount  -> Replicate_State                = 2
                                                

                            Be aware that the Replicate_State object shows a value of 2 in this case.

                            The following list shows the possible values for Replicate_State:

                            • 0 = Replication Not Started. Either no subscribers exist, or Database Layer Monitor service has not been running since subscriber installed.
                            • 1 = Replicates have been created, but their count is incorrect.
                            • 2 = Replication is good.
                            • 3 = Replication is bad in the cluster.
                            • 4 = Replication setup did not succeed.
                            Step 5   To check for network connectivity and DNS server configuration, enter the utils diagnose module validate_network command.

                            Example:
                            utils diagnose module validate_network
                            Log file: /var/log/active/platform/log/diag1.log
                            Starting diagnostic test(s)
                            ===========================
                            test - validate_network: Passed
                            Diagnostics Completed
                                          

                            Change IP address of primary server


                            Warning


                            Using this procedure disrupts all services. Be sure to use it only during a scheduled downtime.

                            Use this procedure to change the IP address of a Cisco MediaSense primary server if your cluster servers are defined using hostnames. To successfully change the IP address, you must complete all steps in this procedure.

                            Procedure
                              Step 1   Review and address the instructions listed in Prepare system for IP Address change before changing the IP address on any Cisco MediaSense server.
                              Step 2   Verify that the DNS change propagates to other servers by using the utils network host and show tech network hosts CLI commands on all servers in the cluster.

                              Example:
                                    
                              utils network host mcs-sec
                              Hostname mcs-sec resolves to 10.10.10.136
                              
                              show tech network hosts
                              -------------------- show platform network --------------------
                              /etc/hosts File:
                              #This file was generated by the /etc/hosts cluster manager.
                              #It is automatically updated as nodes are added, changed, removed 
                              from the cluster.
                              127.0.0.1 localhost
                              1 10.10.10.92 mcs-pri.cisco.com mcs-pri
                              2 10.10.10.93 mcs-sec.cisco.com mcs-sec
                              3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1
                              
                              Step 3   From the primary server, issue the set network cluster server ip command to update the Cisco MediaSense cluster configuration with the primary server’s new IP address.

                              Example:
                                       
                              set network cluster server ip 10.10.10.92 10.10.10.135
                              Setting server ip 10.10.10.92 10.10.10.135
                              Successful
                                              
                              
                              Step 4   Verify the interim cluster configuration by issuing the show network cluster command.

                              Example:
                              show network cluster
                              1 10.10.10.135 mcs-pri Primary not authenticated or updated on server
                              2 10.10.10.93 mcs-sec.cisco.com mcs-sec Secondary authenticated using TCP since Mon Sep 12 12:33:16 2011
                              3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1 Expansion authenticated using TCP since Mon Sep 12 12:33:06 2011
                              - 10.194.118.92 mcs-pri.cisco.com mcs-pri Primary authenticated
                                              
                              
                              Step 5   Point every server in the cluster to the new primary’s IP address by issuing the set network cluster primary ip command from each server in the Cisco MediaSense cluster, including the primary server:

                              Example:
                              set network cluster primary ip 10.10.10.135
                              Setting primary ip to 10.10.10.135
                              Successful
                                              
                              
                              Step 6   Ensure that the IP address change is replicated to the secondary and expansion servers database by entering the run sql select name,nodeid from ProcessNode command on all servers in the cluster. The following example shows the command output:

                              Example:
                              run sql select name,nodeid from ProcessNode
                              name               nodeid
                              ================== ======
                              EnterpriseWideData 1
                              mcs-pri					       2
                              mcs-sec            3
                              mcs-exp1           4
                                            
                              
                              Step 7   If you are moving the primary server to a different subnet that requires a new default gateway address, change the default gateway by issuing the set network gateway command from the primary server:

                              Example:
                              set network gateway 10.3.90.2
                              ***   W A R N I N G   ***
                              This will cause the system to temporarily lose network connectivity
                              Do you want to continue ?
                              Enter "yes" to continue or any other key to abort
                              yes
                              executing...
                                              
                              
                              Note    If you change the default gateway, you may also need to change the subnet mask. See the Unified OS documentation for further details.
                              Step 8   From the primary server, issue the set network ip eth0 command to reset the network adapter to the new IP address.

                              Example:
                                
                              set network ip eth0 <server new ip> <address mask> <gw>
                              set network ip eth0 10.194.118.137.92 255.255.255.0 10.194.118.1
                              
                              ***   W A R N I N G   ***
                              You must first change the IP Address using the
                              <set network cluster server> CLI command BEFORE
                              changing it here or call recording will fail.
                              This will cause the system to restart.
                              
                              =======================================================
                              Note: To recognize the new IP address all nodes within
                              the cluster must be manually rebooted.
                              =======================================================
                              Continue (y/n)? y
                              
                              

                              This command changes the IP address and reboots the primary server.

                              Step 9   Type Yes and press Enter.
                              Step 10   To update the local name resolution files, reboot all other servers in the cluster . Include hosts, rhosts, sqlhosts, and services.
                              Note    Server restart ensures the proper update and service-restart sequence for the IP address changes to take effect.
                              Step 11   Verify that the DNS change propagates to other servers by using the utils network host and show tech network hosts commands on all servers in this cluster.

                              Example:
                                     
                              utils network host mcs-pri
                              Hostname mcs-pri resolves to 10.10.10.135
                              
                              show tech network hosts
                              -------------------- show platform network --------------------
                              /etc/hosts File:
                              #This file was generated by the /etc/hosts cluster manager.
                              #It is automatically updated as nodes are added, changed, removed from the cluster.
                              127.0.0.1 localhost
                              1 10.10.10.135 mcs-pri.cisco.com mcs-pri
                              2 10.10.10.93 mcs-sec.cisco.com mcs-sec
                              3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1
                              
                                            
                              
                              Step 12   Verify the cluster configuration by issuing the show network cluster command.

                              Example:
                              show network cluster
                              1 10.10.10.135 mcs-pri.cisco.com mcs-pri Primary 
                              authenticated using TCP since Mon Sep 12 14:43:59 2011
                              2 10.10.10.93 mcs-sec.cisco.com mcs-sec Secondary authenticated
                              3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1 Expansion 
                              authenticated using TCP since Mon Sep 12 14:44:05 2011
                                              
                              
                              Caution    It may take some time for the cluster to synchronize the new IP address information. During this time, the output for this command may show partial or incomplete information.

                              Change IP address of secondary server


                              Warning


                              This procedure disrupts all services. Be sure to make any changes during a scheduled downtime.

                              Use this procedure to change the IP address of a Cisco MediaSense secondary server if your cluster servers are defined using hostnames. To successfully change the IP address, you must complete all steps in this procedure.

                              Procedure
                                Step 1   Review and address the instructions listed in Prepare system for IP Address change before changing the IP address on any Cisco MediaSense server.
                                Step 2   From the primary server, issue the set network cluster server command to update the Cisco MediaSense cluster configuration with the secondary server’s new IP address.

                                Example:
                                set network cluster server ip 10.10.10.93 10.10.10.136
                                Setting server ip 10.10.10.93 10.10.10.136
                                Successful l
                                
                                                
                                Step 3   Verify the interim cluster configuration by issuing the show network cluster command.

                                Example:
                                show network cluster
                                
                                1 10.10.10.135 mcs-pri.cisco.com mcs-pri Primary 
                                  authenticated using TCP since Mon Sep 12 12:53:16 2011
                                2 10.10.10.136 mcs-sec Secondary not authenticated or updated on server
                                3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1 Expansion 
                                  authenticated using TCP since Mon Sep 12 12:53:06 2011
                                  - 10.194.118.93 mcs-sec.cisco.com mcs-sec Secondary authenticated
                                                
                                
                                Step 4   Point every server in the cluster to the new secondary server IP address by issuing the set network cluster secondary ip command:

                                Example:
                                set network cluster secondary ip 10.10.10.136
                                Setting secondary  ip to 10.10.10.136
                                Successful
                                
                                
                                Step 5   If you are moving the secondary server to a different subnet that requires a new default gateway address, change the default gateway by issuing the set network gateway command from the secondary server:

                                Example:
                                set network gateway 10.3.90.2
                                ***   W A R N I N G   ***
                                This will cause the system to temporarily lose network connectivity
                                Do you want to continue ?
                                Enter "yes" to continue or any other key to abort
                                yes
                                executing...
                                
                                
                                Step 6   Type Yes and press Enter.
                                Step 7   Ensure that the IP address change is replicated to the secondary and expansion server databases by entering the run sql select name,nodeid from ProcessNode command on all servers in the cluster. The following example shows the command output:

                                Example:
                                run sql select name,nodeid from ProcessNode
                                name               nodeid
                                ================== ======
                                EnterpriseWideData 1
                                mcs-pri					       2
                                mcs-sec            3
                                mcs-exp1           4
                                              
                                
                                Step 8   From the secondary server, issue the set network ip eth0 <server new ip> <address mask> <gw> command to set the network adapter to the new IP address.

                                Example:
                                set network ip eth0 10.194.118.137 255.255.255.0 10.194.118.1
                                
                                ***   W A R N I N G   ***
                                You must first change the IP Address using the
                                <set network cluster server> CLI command BEFORE
                                changing it here or call recording will fail.
                                This will cause the system to restart
                                =======================================================
                                Note: To recognize the new IP address all nodes within
                                the cluster will have to be manually rebooted.
                                =======================================================
                                Continue (y/n)? y
                                Step 9   Reboot all servers in the Cisco MediaSense cluster to update the local name resolution files. Include the hosts, rhosts, sqlhosts, and services.
                                Note    Restarting the server ensures that changes occur in proper order for the update and service-restart sequence for the IP address.
                                Step 10   Verify that the DNS change propagates to other servers by using the utils network host command and the show tech network hosts command on all servers in this cluster.

                                Example:
                                utils network host mcs-sec
                                Hostname mcs-sec resolves to 10.10.10.136
                                
                                show tech network hosts
                                -------------------- show platform network --------------------
                                /etc/hosts File:
                                #This file was generated by the /etc/hosts cluster manager.
                                #It is automatically updated as nodes are added, changed, removed from the cluster.
                                127.0.0.1 localhost
                                1 10.10.10.135 mcs-pri.cisco.com mcs-pri
                                2 10.10.10.136 mcs-sec.cisco.com mcs-sec
                                3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1
                                
                                
                                Step 11   Verify the interim cluster configuration by issuing the show network cluster command.

                                Example:
                                1 10.10.10.135 mcs-pri.cisco.com mcs-pri Primary authenticated using TCP 
                                               since Mon Sep 12 14:43:59 2011
                                2 10.10.10.136 mcs-sec.cisco.com mcs-sec Secondary authenticated
                                3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1 Expansion 
                                               authenticated using TCP since Mon Sep 12 14:44:05 2011
                                                
                                

                                Change IP address of expansion server


                                Warning


                                This procedure disrupts all services. Make any changes only during a scheduled downtime.

                                If your cluster servers are defined using hostnames, use this procedure to change the IP address of any expansion servers. To successfully change the IP address, you must complete all steps in this procedure.

                                Procedure
                                  Step 1   Review and address the instructions listed in Prepare system for IP Address change before changing the IP address on any server.
                                  Step 2   From the CLI of the primary server, issue the set network cluster server ip command to update the cluster configuration with the new IP address of the expansion server.

                                  Example:
                                  set network cluster server ip 10.10.10.100 10.10.10.137
                                  Setting server ip 10.10.10.100 10.10.10.137
                                  Successful
                                  
                                  
                                  Step 3   Verify the interim cluster configuration by issuing the show network cluster command.

                                  Example:
                                  show network cluster
                                  1 10.10.10.92 mcs-pri.cisco.com mcs-pri Primary authenticated
                                  2 10.10.10.93 mcs-sec.cisco.com mcs-sec Secondary 
                                                authenticated using TCP since Fri Sep 9 08:52:50 2011
                                  3 10.10.10.137 mcs-exp1 Expansion not authenticated or updated on server
                                                 - 10.10.10.100 mcs-exp1.cisco.com mcs-exp1 Expansion 
                                                 authenticated using TCP since Fri Sep 9 11:40:34 2011
                                  
                                  
                                  Step 4   Ensure that the IP address change is replicated to the secondary and expansion server databases by issuing the run sql select name,nodeid from ProcessNode command on all servers in the cluster. The following example shows the command output:

                                  Example:
                                  run sql select name, nodeid from ProcessNode
                                  name               nodeid
                                  ================== ======
                                  EnterpriseWideData 1
                                  mcs-pri					       2
                                  mcs-sec            3
                                  mcs-exp1           4
                                                
                                  
                                  Step 5   If you are moving the expansion server to a different subnet that requires a new default gateway address, change the default gateway by issuing the set network gateway command from the expansion server:

                                  Example:
                                  set network gateway 10.3.90.2
                                                    
                                  ***   W A R N I N G   ***
                                  This will cause the system to temporarily lose network connectivity
                                  Do you want to continue ?
                                  Enter "yes" to continue or any other key to abort
                                  yes
                                  executing...
                                                  
                                  
                                  Step 6   From the expansion server, issue the set network ip eth0 <server new ip> <address mask> <gw> command to change the IP address of the expansion server.

                                  Example:
                                  set network ip eth0 10.194.118.137 255.255.255.0 10.194.118.1
                                                    
                                  ***   W A R N I N G   ***
                                  
                                  You must first change the IP Address using the
                                  <set network cluster server> CLI command BEFORE
                                  changing it here or call recording will fail.
                                  This will cause the system to restart
                                  =======================================================
                                  Note: To recognize the new IP address all nodes within
                                  the cluster will have to be manually rebooted.
                                  =======================================================
                                  Continue (y/n)? y
                                  

                                  This command changes the IP address and reboots the expansion server.

                                  Step 7   Type Yes and press Enter.
                                  Step 8   To update the local name resolution files, reboot all other servers in the cluster. Include all hosts, rhosts, sqlhosts, and services.
                                  Note    Restarting the server ensures the proper update and service-restart sequence for the IP address changes to take effect.
                                  Step 9   Verify that the DNS change propagates to other servers by using the utils network host and show tech network hosts commands on all servers in this cluster.

                                  Example:
                                  utils network host mcs-exp1
                                  Hostname mcs-exp1 resolves to 10.10.10.137
                                  
                                  show tech network hosts
                                  -------------------- show platform network --------------------
                                  /etc/hosts File:
                                  #This file was generated by the /etc/hosts cluster manager.
                                  #It is automatically updated as nodes are added, changed, removed from the cluster.
                                  127.0.0.1 localhost
                                  1 10.10.10.92 mcs-pri.cisco.com mcs-pri
                                  2 10.10.10.93 mcs-sec.cisco.com mcs-sec
                                  3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1
                                  
                                                
                                  Step 10   Verify the cluster configuration by issuing the show network cluster command.

                                  Example:
                                  show network cluster
                                  1 10.10.10.92 mcs-pri.cisco.com mcs-pri Primary authenticated
                                  2 10.10.10.93 mcs-sec.cisco.com mcs-sec 
                                                Secondary authenticated using TCP since Mon Sep 12 12:33:16 2011
                                  3 10.10.10.137 mcs-exp1.cisco.com mcs-exp1 Expansion 
                                                authenticated using TCP since Mon Sep 12 12:33:06 2011
                                                  
                                  

                                  Change Multiple IP addresses in Cisco MediaSense cluster

                                  Use this procedure to sequentially change the IP addresses for multiple Cisco MediaSense servers. If you use this procedure, you need to issue a series of commands sequentially and reboot only once. To successfully change the IP address for all servers in a cluster, you must complete all steps in this procedure.


                                  Note


                                  This example procedure is written for a three-server cluster. As long as you change the IP addresses on one server at a time, you can modify this procedure for four-server or five-server clusters.



                                  Caution


                                  Change an IP address on only one server at a time. Changing an IP address on more than one server at the same time may cause .hosts files and .sqlhosts files to become out-of-sync.


                                  Warning


                                  Make changes only during a scheduled downtime. Changing IP addresses disrupts all Cisco MediaSense services.
                                  Procedure
                                    Step 1   Review the instructions in Preparing for an IP Address Change before changing the IP address on any Cisco MediaSense server.
                                    Step 2   From the primary server, issue the following commands:

                                    Example:
                                    set network cluster server ip <primary current ip> <primary new ip>
                                    set network cluster server ip <secondary current ip> <secondary new ip>
                                    set network cluster server ip <expansion current ip> <expansion new ip>
                                    set network cluster primary ip <primary new ip>
                                    set network cluster secondary ip <secondary new ip>
                                    
                                    Step 3   From the secondary server, issue the following commands:

                                    Example:
                                    set network cluster primary ip <primary new ip>
                                    set network cluster secondary ip <secondary new ip>
                                    
                                    Step 4   From the expansion server, issue the following commands:

                                    Example:
                                    set network cluster primary ip <primary new ip>
                                    set network cluster secondary ip <secondary new ip>
                                    
                                    Step 5   From the primary server, issue the following commands:

                                    Example:run sql select name,nodeid from ProcessNode
                                    Step 6   From the secondary server, issue the following commands:

                                    Example:run sql select name,nodeid from ProcessNode
                                    Step 7   From the expansion server, issue the following commands:

                                    Example:run sql select name,nodeid from ProcessNode
                                    Step 8   From the primary server, issue the following commands:

                                    Example:
                                    set network gateway (if required)
                                    set network ip eth0 <primary new ip> <address mask>
                                    
                                    Step 9   From the secondary server, issue the following commands:

                                    Example:
                                    set network gateway (if required)
                                    set network ip eth0 <secondary new ip> <address mask>
                                    
                                    Step 10   From the expansion server, issue the following commands:

                                    Example:
                                    set network gateway (if required)
                                    set network ip eth0 <expansion new ip> <address mask>
                                    
                                    Step 11   From each server in the Cisco MediaSense cluster, issue the following commands to verify the cluster configuration.

                                    Example:
                                    utils network host
                                    show tech network hosts
                                    show network cluster