Cisco Unified CCX Administration Guide, Release 9.0(1)
Unified CCX system management
Download this chapter
Unified CCX system managementUnified CCX system management
Download the complete book
Cisco Unified CCX Administration Guide, Release 9.0(1)Cisco Unified CCX Administration Guide, Release 9.0(1) (PDF - 6 MB)
 Feedback

Unified CCX system management

Unified CCX administration provides options to configure, control, and monitor Unified CCX component activities and information across a cluster.


Note

Support for High Availability and remote servers is available only in multiple-server deployments.

See the Installation Guide for Cisco Unified CCX and Cisco Unified IP IVR, Release 9.0(1) for instructions about tasks that significantly change your Unified CCX deployment, such as:

  • Changing from a single-server deployment to a multiple-server deployment.
  • Removing a Unified CCX Software component from a server.
  • Moving a Unified CCX Software component to another server.
  • Changes to a Unified CCX cluster (adding, removing, or replacing a server).

The following sections describe the day-to-day management of Unified CCX components.

Basic terminology

This section provides information about different Unified CCX terminology.

  • Cluster. A Unified CCX cluster (often referred to as cluster in this manual) consists of one or more servers (nodes) that are running Unified CCX components in your Unified CCX deployment. If you deploy Unified CCX components on a single server, the Unified CCX cluster consists of that server. If you deploy Unified CCX on multiple servers, the cluster includes the Unified CCX server and standby server on which you installed Unified CCX. The Unified CCX cluster supports up to two Unified CCX servers, one designated as the active Unified CCX server and the other designated as the standby Unified CCX server for high availability purposes.

    Note

    Support for High Availability and remote servers is available only in multiple-server deployments.

  • Cluster profile. The Unified CCX Administration web page (home page) displays information about the cluster profile. A cluster profile includes data relating to the Unified CCX servers, components, and licenses installed in a cluster.
  • Node (server). A server that is part of the Unified CCX cluster.
  • Active Server. The active server provides all system services and resources. You can deploy one active server in each Unified CCX subsystem. If the active server fails, the Unified CCX subsystem automatically fails over to the standby server.
  • Standby Server. You can deploy up to two servers in each Unified CCX system for high availability—one active server (master) and one standby (not active) server. With high availability, if an active server becomes unavailable, the standby server automatically becomes the active server.
  • Component.The software units in the Unified CCX system. The main software components of the Unified CCX server are the Engine, datastores, monitoring, recording, and the Cluster View Daemon (CVD). See the Installation Guide for Cisco Unified CCX and Cisco Unified IP IVR, Release 9.0(1) for more information on setup and installation procedures.
  • Service. An executable unit. A service may have other services as its children. (For example, subsystems and managers are children of the engine service).
  • Feature. A logical representation of the functional unit.
  • Master service. A specially-elected service. Only one service from the Engine service, desktop services, or database services set can be the master within the Unified CCX Engine component. See the Cisco Unified Contact Center Express Serviceability Guide for detailed information on services.
  • Standby service. An active service that can take over the master functionality in case the master service becomes unavailable within the Unified CCX Engine component. You cannot configure the standby service. The Cluster View Daemon (CVD) dynamically elects the services on the active node to be the master. See the Cisco Unified Contact Center Express Serviceability Guide for detailed information on services.
Related References

High availability and automatic failover


Note

Support for High Availability (HA) and remote servers is available only in multiple-server deployments. Unified CCX does not support more than two nodes in a HA setup. Expansion servers where the Database, Monitoring, or Recording components are running on separate servers are not supported.

Unified CCX provides high availability and automatic failover capability through the use of two servers, the active server and the standby server.

The active server provides all system services and resources; no services or resources are available from the standby server. When you make administrative changes on the active server, both the servers are synchronized.

If the active server fails, there is automatic failover to the standby server. For detailed information on HA over WAN deployment, see Cisco Unified CCX Solution Reference Network Design.

Network partitions

Network malfunction or misconfiguration can create network partitions and split the network into separate islands. If a node enters this state, the node is referred to as being in the island mode. Nodes in the island mode are hard to detect. While these nodes can communicate within a partitioned island, they cannot communicate between partitioned islands. If the islands do not communicate, then each island will select its own active server.

Generally, you can connect to the Unified CCX administration on any node, and see a consistent cluster view. If a node is in the island mode, you will see different cluster views when you connect to nodes in each island.


Note

Support for High Availability and remote servers is available only in multiple-server deployments.

If your node enters the island mode, it should recover from the island mode as soon as the underlying network issue is resolved. If the island mode persists, check the network connectivity/reachability between the two CCX servers and take action accordingly.

Unified CCX CDS information management

The Unified CCX system stores configuration information in the Cisco Configuration Datastore Server (CDS). The Unified CCX Administration configurations are stored in the CDS.


Note

Support for High Availability and remote servers is available only in multiple-server deployments.

The Unified CCX server can receive directory information from one Cisco Unified Communications directory and application configuration and script logic from a repository on another server. See Cisco Unified Contact Center Express Serviceability Guide for detailed information.

Manage system parameters

The parameters in the System Parameters Configuration page are grouped logically into sections with headings. Each parameter has a corresponding suggested or default value on the right side of the page. Where applicable, radio buttons are used to toggle between the parameter options.

In this web page, you can configure the number of historical reporting clients, the recording count, port settings, the default session timeout, and codec.


Note

Changing some system parameters like IP address, Network Time Protocol (NTP) and so on can result in a different License MAC. You need to get rehosted license files (with new License MAC) in such cases within 30-day grace period beyond which the system will stop working.

Procedure
    Step 1   Choose System > System Parameters from the Unified CCX Administration menu bar.

    The System Parameters Configuration web page appears.

    Step 2   Click the Update icon that displays in the tool bar in the upper, left corner of the window or the Update button that displays at the bottom of the window.

    The system notifies all nodes in the cluster about the changes.

    Note   

    If Cluster View Daemon is in Shutdown state during this operation, then the changes just made are synchronized on that node when Cluster View Daemon is started again.

    Related References

    System parameters configuration web page

    The System Parameters Configuration web page displays the following fields.

    Table 1 System Parameters Configuration
    Field Description

    Generic System Parameters

    System Time Zone

    The system or primary time zone will be the same as local time zone of the primary Unified CCX node configured during installation. Display only. Unified CCX Administration uses this primary time zone to display time-related data.

    Note   

    If you have changed the primary time zone, you need to reboot both the nodes in the Unified CCX cluster.

    Network Deployment Parameters (displayed only in a HA over WAN deployment)

    Network Deployment Type

    Displays the network deployment type as LAN or WAN only if we have more than one node. Display only.

    Internationalization Parameters

    Customizable Locales

    Use to specify a unique locale.

    Default: (blank)

    Default Currency

    Default currency, such as American dollars (USD), Euros, and so on. This is a mandatory field.

    The system uses the default currency for converting currency amounts in a playable format when no currency designator is specified.

    Default: American Dollar [USD]

    Media Parameters

    Codec

    The codec chosen during installation for this Unified CCX server.

    Unified CCX supports packetization intervals of 20 ms, 30 ms, or 60 ms only.

    Default: 30 ms

    Recording Count

    The maximum number of simultaneous sessions that are supported with this system configuration. This value cannot be greater than the number of seats. This is a mandatory field.

    Note   

    Standard license package does not support recording. Premium package license supports recording, however, when you upgrade from Standard to Premium license package, you need to manually change this recording count to a suitable value based on the hardware type to enable recording functionality.

    Default: 0

    Default TTS Provider

    Default TTS (Text-to-Speech) provider.

    Default: By default, no TTS provider is configured. Select a provider from the drop-down list to configure it as the default. The system uses the default TTS provider to determine which provider to use if the TTS request does not explicitly specify the provider to use.

    User Prompts override System Prompts When enabled, custom recorded prompt files can be uploaded to the appropriate language directory under Prompt Management to override the system default prompt files for that language. By default, this is disabled.

    Application Parameters

    Supervisor Access

    The Administrator uses this option to allow certain privileges to supervisors (all supervisors have the same privilege). The options are:

    • No access to teams—The supervisor logs into the Supervisor page, but will not be able to see any team information (No RmCm info).
    • Access to all teams—The supervisor logs into the Supervisor page, and will be able to see all the teams (RmCm information).
    • Access to supervisor teams only—The supervisor logs into the Supervisor page, and will be able to see the teams they supervise.

    Default: No access to teams

    Note   

    A supervisor who does not have administrator privileges can add, modify, or remove skills from an agent.

    Max Number of Executed Steps

    The maximum number of steps an application can execute before the Unified CCX Engine terminates the script or application. This is a mandatory field.

    This limitation is intended to prevent a script from running indefinitely.

    Default: 1000

    Note   

    Do not change the default value.

    Additional Tasks

    This field allows you to control the creation of additional threads that the Unified CCX server internally initializes based on licensed Unified IP IVR ports. This is a mandatory field.

    Default: 0

    Default Session Timeout

    Maximum amount of time (in minutes) a user-defined mapping ID remains in the session object memory after the session is moved to the idle state. During this duration, the session continues to be accessible even if you have terminated that session. Use this setting to configure the time required to perform your after-call work (for example, writing variables to a database before clearing the session). This is a mandatory field.

    The default is 30 minutes (recommended). If you reduce this number, you also reduce the system memory usage comparatively.

    You can add a user-defined mapping ID to a session using the Session Mapping step in the script editor. Once assigned, you can use this mapping ID to get the session object from another application instance. By doing so, other applications obtain access to the session context. See the Cisco Unified CCX Getting Started with Scripts guide for more information.

    Enterprise Call Info Parameter Separator

    A character used Get/Set Enterprise Call Info steps in the Unified CCX Editor to act as a delimiter for call data. This is a mandatory field.

    Default: | (bar)

    Agent State after Ring No Answer

    Radio button determining how agent state should be set after a Ring No Answer event. This is a mandatory field. The choices are:

    • Ready. If an agent does not answer a call, the Agent State is set to Ready.
    • Not Ready (default). If an agent does not answer a call, the Agent State is set to Not Ready.

    Number of HR session licenses

    The number of Historical Reporting sessions that can be supported with this system configuration. This denotes the number of historical reporting clients that can be started simultaneously on different client machines. This is a mandatory field.

    This value cannot be greater than the number of licensed seats in the case of Unified CCX (see Configure database server limits).

    Default: 0 for Unified CCX (Standard, Enhanced, and Premium), 5 Unified IP IVR.

    Number of Outbound seats

    The maximum number of Outbound seats. The configuration of Outbound seats is done during the initial configuration or setup phase, after the installation.

    Note   

    This is a mandatory field. This field is displayed only if you have a Premium license.

    The maximum number of preview outbound seats that can be configured is limited by either the Premium Seat Count or the hardware limit, whichever is the least. If there is an invalid entry during configuration, an error message is displayed.

    The max count for the Preview Outbound seat count is as shown in the table

    System Ports Parameters

    RMI Port

    The port number used by the Unified CCX CVD to serve RMI requests. This is a mandatory field.

    Default: 6999

    RmCm TCP Port

    TCP port number on which the CTI server component of the RmCm subsystem opens the server socket and listens to the clients. All CTI server clients, such as Cisco Agent Desktop, Unified ICME Server, Sync Server, and IP Phone Agent Server, use this port number. This is a read-only field and cannot be modified.

    Default: 12028

    Master Listener TCP Port

    TCP port used for communication between CVD and Cisco Agent/Supervisor Desktop Services. This is a read-only field and cannot be modified.

    Default: 1994

    Related References

    Unified CCX IP address management

    This section provides the steps you need to follow whenever there is a change in IP address for the following Unified CCX deployments:

    • Unified CCX Cluster with Single-node
    • Unified CCX Cluster with High Availability (HA)

    You may want to change the IP address for a variety of reasons, including moving the server from one segment to another or resolving a duplicate IP address problem.


    Note

    Host name change is not supported in Cisco Unified CCX 9.0(1).

    Prepare system for IP address change

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


    Note

    If you do not receive the results that you expect when you perform these tasks, do not continue with this procedure until after you resolve any problems that you find. DB replication across the entire cluster is essential for this process.

    Procedure
      Step 1   List all servers in the cluster and note whether the nodes are defined by using IP addresses or host names.
      • From Cisco Customer Response Solutions menu bar on the first node, navigate to System > Server. A list of all servers in the cluster displays.
      • See whether the servers are defined using IP addresses or host names and capture this list of servers for later reference. Ensure that you have saved an inventory of both the host name and IP address of each node in your cluster.
      Step 2   Ensure that all servers in the cluster are up and available by checking for any active ServerDown alerts. You can check by using either the Real Time Monitoring Tool (RTMT) or the Command Line Interface (CLI) on the first node.
      • To check by using RTMT, access Alert Central and check for ServerDown alerts.
      • To check by using the CLI on the first node, enter the following command and inspect the application event log: file search activelog syslog/CiscoSyslog ServerDown
      Step 3   Check the DB replication status on all the Cisco CRS nodes and Cisco Unified Communications nodes in the cluster to ensure that all servers are replicating database changes successfully using the following substeps:
      1. For Unified CCX: In a High Availability deployment of Unified CCX, you can check the DB replication status for the datastores across all servers in the cluster using Unified CCX Serviceability Administration. Choose Tools > Datastore Control Center > Replication Servers from the Unified CCX Serviceability menu bar to view the replication status. The value in State field for both the servers in this web page should display ACTIVE/ CONNECTED. Refer to Cisco Unified Contact Center Express Serviceability Guide for more information on how to reset replication.
      2. For Cisco Unified Communications Platform: You can check the DB replication status on all the Cisco Unified Communications nodes in the cluster by using either RTMT or a CLI command.
        • To check by using RTMT, access the Database Summary and inspect the replication status.
        • To check by using the CLI, enter the command that is shown in the following example: 
        admin: 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 the Database Layer Monitor service is not running and has not been running since the subscriber was 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 4   Run a manual DRS backup and ensure that all nodes and active services are backed up successfully. For more information, refer to Disaster Recovery System Administration Guide for your release.
      Step 5   Run the CLI command utils diagnose module validate_network through Platform CLI on all nodes in the cluster to ensure network connectivity and DNS server configuration are intact.

      IP address modification

      This section describes how to change the IP address.


      Caution

      Changing the IP address on any node in a Cisco CRS cluster can interrupt call processing and other system functions. Also, changing the IP address can cause the system to generate certain alarms and alerts such as ServerDown and automatic failover to a backup server may not operate. Because of this potential impact to the system, you must perform IP address changes during a planned maintenance window.

      Change IP address for server in single-node deployment

      Use this procedure to change the IP address of the server in a single-node deployment.

      Procedure
        Step 1   Change the DNS record of the server to point to the new IP address. Ensure that you correctly update both the forward (A) and reverse (PTR) records, and there are no duplicate PTR records.
        Note   

        Skip Step 2 if the server is defined by host name and you are changing only the IP address.

        Step 2   From Cisco Customer Response Solutions menu bar, perform the following tasks:
        1. Navigate to System > Server. Click the IP address of the server.
        2. The Server Configuration page for the server opens. Enter the new IP address in the Host Name/IP Address field and click Save.
        Step 3   If you are moving the server to a different subnet that requires a new default gateway address, you can change the default gateway and IP address using either CLI command or through Cisco Unified Communications Operating System Administration interface as explained below:

        Using CLI command:

        1. To change the default gateway, enter the following CLI command: set network gateway <IP Address>

          The following sample output displays: 

          admin: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...
admin:
          Note   

          Ensure that the server is moved to the new subnet and has access to the default gateway before proceeding to the following sub-step.

        2. To change the IP address of the server, enter the following CLI command: set network ip eth0 <ip_address> <netmask>

          where ip_address specifies the new server IP address and netmask specifies the new server network mask.

          The following sample output displays: 

          admin: set network ip eth0 10.3.90.21 255.255.254.0
** W A R N I N G ***
If there are IP addresses (not hostnames)
configured in UCCX Administration
under System -> Servers then you must change
the IP address there BEFORE changing it here
or call processing 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.
=======================================================
Do you want to continue?
Enter "yes" to continue and restart or any other key 
to abort

          Enter y and press Enter. This will automatically reboot this server with the new IP address.

          Through Cisco Unified Communications Operating System Administration Interface:

          Alternatively, you can change the IP address and default gateway of the server from Cisco Unified Communications Operating System Administration interface using the following substeps:
          • Choose Settings > IP > Ethernet.
          • Change the IP address, default gateway, and netmask, and click Save. The server reboots automatically with the new IP address.
        Step 4   If you change the IP address, License MAC of the server will also change. Rehost the new license. Old license enters its grace period.
        Step 5   From Cisco Desktop Administrator web page, choose Services Configuration > Silent Monitoring & Recording > Remove VoIP/Recording & Playback Services. Remove any VoIP Monitor Service or Recording & Playback Service listed, which uses the IP address that has been changed.
        Step 6   From Cisco Desktop Administrator, navigate to CAD Configuration Setup. Update primary location of the CAD-BE Server to the new IP address. The Services IP Address should display the new IP address. If not, change it to the new IP address. Click Save and then restart all CAD services on the server after making these updates.
        Note   

        When you change the IP address in a single-node deployment, CAD does not launch itself and you need to run the Cisco Unified CCX Desktop Client Configuration tool to update the client installations with the new IP address.

        Related Tasks

        IP address modification in high-availability (HA) deployment

        Use the following subsections to change the IP address of publisher and subscriber in a HA deployment:

        Change IP address for publisher server in HA deployment

        Use this procedure to change the IP address of publisher server in a HA deployment.

        Procedure
          Step 1   Change the DNS record of the publisher server to point to the new IP address. Ensure that you correctly update both the forward (A) and reverse (PTR) records, and there are no duplicate PTR records.
          Step 2   Verify that the DNS change propagates to other nodes by using the utils network host and show tech network hosts CLI commands on all the cluster nodes.
          Note   

          Skip Step 3 if the server is defined by host name and you are changing only the IP address.

          Step 3   From Cisco Customer Response Solutions menu bar of the publisher server, perform the following tasks:
          1. Navigate to System > Server. From the List Servers web page, click the IP address of the publisher server.
          2. The Server Configuration page for the publisher server opens. Enter the new IP address in the Host Name/IP Address field and click Save.
          Step 4   From the Cisco Unified Operating System Administration web page of the subscriber server in the cluster, perform the following tasks:
          1. Navigate to Settings > IP > Publisher.
          2. Change the IP address of the publisher server.
          Step 5   To update new IP of the publisher server in subscriber, enter the following CLI command on the subscriber server: 
          utils uccx modify remote_IPAddress <Old_IP_of_Publisher>
<New_IP_of_Publisher>

          The following output displays: 

          admin:utils uccx modify remote_IPAddress 10.3.90.21  10.3.90.28

 Old Remote IP Address: 10.3.90.21
 New Remote IP Address: 10.3.90.28

This command should be executed only in case you are changing IP Address of remote server.
Are you sure you want to run this command?
Continue (y/n)?

          Enter y and press Enter.

          Step 6   If you are moving the publisher server to a different subnet that requires a new default gateway address, you can change the default gateway and IP address using either CLI command or through Cisco Unified Communications Operating System Administration interface as explained below:

          Using CLI command:

          1. To change the default gateway, enter the following CLI command: set network gateway <IP Address>

            The following sample output displays: 

            admin: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...
admin:
            Note   

            Ensure that the server is moved to the new subnet and has access to the default gateway before proceeding to the following sub-step.

          2. To change the IP address of the server, enter the following CLI command: set network ip eth0 <ip_address> <netmask>

            where ip_address specifies the new server IP address and netmask specifies the new server network mask.

            The following sample output displays: 

            admin: set network ip eth0 10.3.90.21 255.255.254.0
** W A R N I N G ***
If there are IP addresses (not hostnames)
configured in UCCX Administration
under System -> Servers then you must change
the IP address there BEFORE changing it here
or call processing 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.
=======================================================
Do you want to continue?
Enter "yes" to continue and restart or any other key to abort

            Enter y and press Enter. This will automatically reboot this server with the new IP address.

            Through Cisco Unified Communications Operating System Administration Interface:

            Alternatively, you can change the IP address and default gateway of the server from Cisco Unified Communications Operating System Administration interface as follows:
            • Choose Settings > IP > Ethernet.
            • Change the IP address, default gateway, and netmask, and click Save. The server reboots automatically with the new IP address.
          Step 7   Reboot all other servers in the cluster using the CLI command utils system restart.
          Step 8   If you change the IP address, License MAC will also change. Rehost the new license for the new LicenseMAC. Old license enters its grace period.
          Step 9   From Cisco Desktop Administrator web page, choose Services Configuration > Silent Monitoring & Recording > Remove VoIP/Recording & Playback Services. Remove any VoIP Monitor Service or Recording & Playback Service listed, which uses the IP address that has been changed.
          Step 10   From Cisco Desktop Administrator, navigate to CAD Configuration Setup. Update primary and secondary location of the CAD-BE Servers to the new IP address. The Services IP Address should display the new IP address. If not, change it to the new IP address. Click Save and then restart all CAD services on the server after making these updates.
          Note   

          When you change the IP address of publisher, CAD will connect to the subscriber and will update the IP address of the publisher automatically through its True Update functionality.

          Related Tasks
          Change IP address for subscriber server in HA deployment

          Use this procedure to change the IP address of a subscriber server in a HA deployment.

          Procedure
            Step 1   Change the DNS record of the subscriber server to point to the new IP address. Ensure that you correctly update both the forward (A) and reverse (PTR) records, and there are no duplicate PTR records.
            Step 2   Verify that the DNS change propagates to other nodes by using the utils network host and show tech network hosts CLI commands on all the cluster nodes.
            Note   

            Skip Step 3 if the server is defined by host name and you are changing only the IP address.

            Step 3   From Cisco Customer Response Solutions menu bar, perform the following tasks:
            1. Navigate to System > Server. From the List Servers web page, click the IP address of the subscriber server.

              The Server Configuration page for the subscriber server opens.

            2. Enter the new IP address in the Host Name/IP Address field and click Save.
              Note   

              You can use the CLI command run sql select name,nodeid from ProcessNode to check whether the new IP address has been replicated on all the servers.

            Step 4   To update new IP of the subscriber in publisher, enter the following CLI command on the publisher server:

            utils uccx modify remote_IPAddress <Old_IP_of_Subscriber> <New_IP_of_Subscriber>

            The following output displays: 

            admin:utils uccx modify remote_IPAddress 10.3.90.21  10.3.90.28

 Old Remote IP Address: 10.3.90.21
 New Remote IP Address: 10.3.90.28

This command should be executed only in case you are changing IP 
Address of remote server.
Are you sure you want to run this command?
Continue (y/n)?

            Enter y and press Enter.

            Step 5   If you are moving the server to a different subnet that requires a new default gateway address, you can change the default gateway and IP address using either CLI command or through Cisco Unified Communications Operating System Administration interface as explained below:

            Using CLI command:

            1. To change the default gateway, enter the following CLI command: set network gateway <IP Address>

              The following sample output displays: 

              admin: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...
admin:
              Note   

              Ensure that the server is moved to the new subnet and has access to the default gateway before proceeding to the following sub-step.

            2. To change the IP address of the server, enter the following CLI command: set network ip eth0 <ip_address> <netmask>

              where ip_address specifies the new server IP address and netmask specifies the new server network mask.

              The following sample output displays: 

              admin: set network ip eth0 10.3.90.21 255.255.254.0
** W A R N I N G ***
If there are IP addresses (not hostnames)
configured in UCCX Administration
under System -> Servers then you must change
the IP address there BEFORE changing it here
or call processing 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.
=======================================================
Do you want to continue?
Enter "yes" to continue and restart or any other key to abort

              Enter y and press Enter. This will automatically reboot this server with the new IP address.

            Through Cisco Unified Communications Operating System Administration Interface:

            Alternatively, you can change the IP address and default gateway of the server from Cisco Unified Communications Operating System Administration interface as follows:

            1. Choose Settings > IP > Ethernet.
            2. Change the IP address, default gateway, and netmask, and click Save. The server reboots automatically with the new IP address.
            Step 6   Reboot all other servers in the cluster using the CLI command utils system restart.
            Step 7   From Cisco Desktop Administrator web page, choose Services Configuration > Silent Monitoring & Recording > Remove VoIP/Recording & Playback Services. Remove any VoIP Monitor Service or Recording & Playback Service listed, which uses the IP address that has been changed.
            Step 8   From Cisco Desktop Administrator, navigate to CAD Configuration Setup. Update primary and secondary location of the CAD-BE Servers to the new IP address. The Services IP Address should display the new IP address. If not, change it to the new IP address. Click Save and then restart all CAD services on the server after making these updates.

            Verify proper function of system after IP address change

            Once you change the IP addresses of your cluster, complete the following tasks:

            Procedure
              Step 1   Choose Tools > Plug-ins and click Cisco Unified CCX Desktop Suites from the Unified CCX Administration menu bar. From the Cisco Unified CCX web page, run the Cisco Unified CCX Desktop Client Configuration tool to update the client installations with the new IP addresses.

              On the client, if only one IP address in a HA system has been updated and the client is an XP machine with administrator privileges, then the Automatic Update process will update the registry the next time the user logs on. However, you will have to manually update the client's system by running C:\Program Files\Cisco\Desktop\bin\PostInstall.exe program, and update it with the correct IP addresses, if any of the following conditions are true:

              • IP address of a single-node deployment is changed
              • Both IP addresses in a HA system is changed
              • Client OS is Microsoft Vista or Win7
              • Client does not have administrative rights
              Step 2   Ensure that all the servers in the cluster are up and available.
              Step 3   Check the DB replication status as described in Step 3 of Prepare system for IP address change to ensure all the servers are replicating database changes successfully.
              Step 4   Run a manual DRS Backup and ensure that all nodes and active services are successfully backed up.
              Step 5   Run the CLI command utils diagnose module validate_network through platform CLI on all nodes in the cluster to ensure network connectivity and DNS server configuration are intact.
              Step 6   If you have changed the IP address to move the Unified CCX server to a different network, then any firewall configuration on the other network must be changed to permit or deny traffic from the new IP address.
              Step 7   If you have created any DSN using old IP address, change the DSN to point to the new IP. For example, the DSN created for Wallboard.
              Step 8   Update the new IP address in the following web pages as well:
              • Cisco Desktop Administrator > Cisco Unified Presence Settings > Cisco Unified Presence Cluster - Publisher Host/IP Address and Subscriber Host/IP Addresses
              • Cisco Desktop Administrator > Agent E-Mail Settings > Global Settings - IMAP Server Host/IP Address and SMTP Server Host/IP Address
              • Work Flow Configuration > User Interface > Browser Setup - URL and Home Page
              • Work Flow Configuration > HTTP Action - Host
              • Work Flow Configuration > IPC Action - IP Address

              Exit Unified CCX administration

              To exit Unified CCX Administration without closing your web browser, you can do either of the following:


              Note

              You can also exit Unified CCX Administration by closing your web browser.

              Procedure
                Step 1   Click the Logout link displayed in the top right corner of any Cisco Unified CCX Administration web page
                Step 2   Choose System > Logout from the Unified CCX Administration menu bar.

                The system logs you out of Unified CCX and displays the Unified CCX Authentication web page.