CCE Orchestration

Overview

The Orchestration feature provides partners and administrators an option to automatically download software updates and simplify the installation and rollback processes. The Orchestration framework is built within the Cloud Connect server that connects to the Cisco hosted cloud software repository. This framework provides the ability to check and download new software updates as and when they are available and notify the administrators via email about the new updates along with the release notes. Orchestration currently supports installation and rollback of Cisco Engineering Specials (ES), Service Updates (SU), Minor Releases (MR), and Microsoft Patches.

Email Notification

The Cloud Connect server checks for new software updates daily at a predefined time. When the new software updates are available, an email notification is sent. This email notification consists of available software updates details along with the release notes and is triggered to the administrators who have subscribed for it.

Email notifications are also sent to provide updates on the success and failure of any upgrade, rollback, or switch forward procedure. These notifications include details such as:

  • Specific nodes on which the upgrade, rollback, or switch forward is initiated.

  • Cloud Connect server name from where the procedure is triggered.

  • Time (Cloud Connect server time) at which the procedure is started.

  • Details about build versions of the respective nodes. For example, for an upgrade procedure, it shows both the version from which it is upgraded (FromVersion) and the version to which it is upgraded (ToVersion).

  • Status of the procedure for respective nodes to indicate whether the procedure is successful or has failed; the subject line of the email indicates the overall status: success, failure, or partial success.

    Cloud Connect server downloads the available software from Cisco software repository every day at 02:00 A.M. server time. Email notification is triggered from Cloud Connect server to subscribed users with software download failure details. Also, Cisco software artifactory will trigger an email notification with entitlement or compliance failure details to the email address mapped to CCO ID that is used to generate the Artifactory API key.


    Note

    • If the option "All nodes" is selected during the upgrade, an email notification is sent about the success or failure at each stage of upgrade.

    • The name of the deployment is shown in the subject line of the email, depending on the configuration in the inventory file.

    • For patch install or rollback, email notifications are not sent to indicate whether the procedure is successful or if it is a failure.

Orchestration in CCE Deployment

The Orchestration feature is part of the Cloud Connect node that is configured in the CCE deployment.

System Requirements

Orchestration is supported from Cloud Connect 12.6(1) onwards.

VOS Component Upgrade

Refer below for the minimum software version required to enable this feature for the following components:

  • Finesse

  • CUIC/LD/IDS/Co-resident

  • VVB

Apply the cop ucos.orchestration.enable-12.5.1.cop.sgn on the above-mentioned components with 12.5(1) version to on-board and orchestrate VOS nodes from Cloud Connect server.


Note

The cop must be applied on both the publisher and subscriber nodes.

Note

After you install a patch on target VOS node, you will not be able to run commands in the same session. You must restart the session to use the Orchestration CLI commands.


Note

Before intitiating 12.6(1) upgrade on VOS nodes from Orchestration, install the Mandatory COP ucos.keymanagement.cop.sgn from Orchestration on target 12.5(1) VOS nodes.

Windows Component Upgrade

Manually install mandatory ES66 on ICM 12.5 (1) and ES20 on CVP 12.5 (1) to on-board and orchestrate Windows nodes from Cloud Connect server.


Note

For version 12.5(1) VOS and Windows nodes, the ES and COP files are required for onboarding and Orchestration. The same files are not required if the target nodes are already on 12.6(1).

Orchestration Support using Cloud Connect Server

Cloud Connect server version 12.6 (1) supports orchestration in the following scenarios:

  • CCE 12.5 ES/COP and Windows Updates can be orchestrated from 12.6 Cloud Connect server

  • CCE 12.5 to 12.6 software upgrade can be orchestrated from 12.6 Cloud Connect server

  • CCE 12.6 ES/COP and Windows Updates can be orchestrated from 12.6 Cloud Connect server

See System Requirements for minimum software requirement to enable orchestration for the above supported model.

Parallel Execution of CLI

Parallel execution of same or different CLIs on Cloud Connect server is disabled for Orchestration. However, parallel execution is allowed for the following commands:

  • utils deployment show in-progress

  • utils system inventory export

  • utils system inventory import

  • email configuration commands

  • utils deployment show progress-HA

  • email configuration-related commands, see Configure Email Notification.

Administration Task Flow

Check Installed Software Version and Patches
Install or Rollback Patch for Cloud Connect Server
List Available Patches for Specific Node or Group of Nodes
Install Patch to Specific Node or Group of Nodes
Roll Back Patch from Specific Node or Group of Nodes
Install Windows Updates to Specific Node or Group of Nodes
Roll Back Windows Update from Specific Node or Group of Nodes
Enable or Disable Compatibility Enforcement
Initiate maintenance mode for a specific node
List Available Upgrade Options
Upgrade a Specific Node or Group of Nodes or All Nodes
Perform Switch Forward on Specific VOS Node or Group of Nodes
Roll Back Upgrade from Specific Node or Group of Nodes
Check Last Known Orchestration Operation Status on Remote Node
Check Status
Start ICM Services

Deployment Tasks

Generate the Artifactory API Key

To generate the Artifactory API Key, follow the steps below:


Note

It is mandatory for the CCO ID used to generate API keys to have necessary software upgrade entitlements. The CCO ID used by the partner or customer should have a valid SWSS (service contract) or Flex subscription in order to have the necessary entitlement.

  • Login to https://devhub-download.cisco.com/console/ using your CCO Username and Password.

  • Navigate to 'Manage Download Key page.

  • Click Generate Key option to Generate the API key. Option to View and Revoke Key is available in Manage Download Key page.

  • Click on the Copy option to copy the API key to the clipboard.


    Note

    You must log into https://devhub-download.cisco.com/console once every six months to extend the validity of the API key.

CLI to configure Artifactory URL and API Key

Cisco hosts all the software artifacts in a cloud-based artifactory which is used by Cloud Connect server to download and notify new updates.

Cloud Connect server should be configured with Cisco hosted software Artifactory URL, Repository Name, and API Key. Run the utils image-repository set command. Refer to the Set Command table.

To view the configured Artifactory URL, Repository Name, and API Key in the Cloud Connect server, run the utils image-repository show command. Refer to the Show Command table.


Note

Both these commands can be executed only from the publisher node of the Cloud Connect server. The replication of image repository configuration occurs automatically from the publisher node to the subscriber node when the utils image-repository set command is executed with successful results on the publisher node.

Table 1. Set Command Table
Command utils image-repository set
Description This command allows the user to configure the Cisco hosted software Artifactory URL, Artifactory Repository Name, and API Key. For information on API Key, refer to the Generate the JFrog Artificatory API Key section.

This command validates the below:

  • If the CCO ID used to generate the API key has entitlement to download the Contact Center software.

  • If the End User License Agreement has been signed by the customer.

  • If the user has registered and successfully validated the customer company details with Cisco.

  • If the Cloud Connect server is deployed in embargoed countries where software download is restricted.

  • If the user has valid authentication token associated with the API key.

If the user does not have a valid authentication token associated with the API key, then the user has to login to https://devhub-download.cisco.com/console/ to extend the validity of the API key.

Expected Inputs

User should input Artifactory URL, Artifactory Repository Name, and API Key.

The Cisco hosted software Artifactory URL and Artifactory Repository name values are https://devhub-download.cisco.com/binaries and ent-platform-release-external.

CLI will provide an option to customer to choose between using export restricted vs unrestricted software in deployment based on the entitlement associated with the CCO ID. For example VVB has export restricted and un-restricted software.

Expected Outcome This CLI validates the entitlement associated with the CCO ID and connection to the Cisco hosted software artifactory using the given configuration. Based on successful validation, the artifactory details are configured in the Cloud Connect server.

Note

The utils image-repository set CLI can be used anytime to change using export restricted vs unrestricted software in the deployment. Restart the Cloud Connect server to enforce the cleanup and download of restricted vs unrestricted software. Download starts 10 minutes post restart.


Note

Upon successful configuration of artifactory details, artifacts will be downloaded locally to the Cloud Connect server at 02:00 A.M. server time. Orchestration operations such as patch install, rollback or upgrade can be performed only after the artifacts are downloaded. If the artifacts have to be downloaded immediately after the configuration, then the Cloud Connect server can be restarted and the download starts 10 minutes post restart. Usage of orchestration related CLI are blocked during download, and this duration depends on the number of artifacts to be downloaded.

Table 2. Show Command Table
Command utils image-repository show
Description This command is used to show the configured Cisco hosted software Artifactory URL, Repository Name, and the API Key (the mix of hash and last 4 characters of key) in the Cloud Connect server.
Expected Inputs NA
Expected Outcome Shows the configured Artifactory URL, Repository Name, and the API Key.

Onboard VOS Nodes to Orchestration Control Node

The onboarding process helps to establish a password-less connection between the Cloud Connect node and the VOS nodes.

Prerequisites:

  • Ensure that the Cloud Connect server and target nodes maintain the minimum software versions that are required as outlined in System Requirements.

  • If you are using self-signed certificates, import the self-signed Tomcat certificate of the Cloud Connect server into the VOS nodes which you have to onboard. Ensure to import both Cloud Connect publisher and subscriber node certificates on all VOS publisher and subscriber nodes. For details, see Self-Signed Certificate.

To onboard Finesse, CUIC, VVB, IDS, LD to a Cloud Connect server, run the utils system onboard initiate command from the publisher node of the respective VOS cluster that you wish to onboard. The publisher node of the Cloud Connect server must be up and running when onboarding is initiated from VOS node. When the onboarding is initiated from VOS node, FQDN of the Cloud Connect server must be used.

Command utils system onboard initiate
Description This command is used to onboard a VOS node such as Finesse, CUIC, VVB, etc., to a Cloud Connect server.
Expected Inputs When executed, the command prompts for:

  • Cloud Connect server FQDN

  • Cloud Connect application username

  • Password
Expected Outcome The nodes are onboarded to the Cloud Connect server orchestration inventory. A message is displayed indicating the status.

Note

If the system (cluster) onboards to the Cloud Connect server with partial error, check the reason for the error and correct it. Then, run the utils system onboard update command instead of running the utils system onboard initiate command.


Note

Onboarding is allowed only when all the publisher and subscriber nodes in the Cloud Connect server are reachable.


Note

If the Cloud Connect server is corrupted and redeployed by doing fresh install, the administrator has to run utils system onboard remove from the VOS node and then run utils system onboard initiate to onboard the VOS nodes again.

Onboard Windows Nodes to Orchestration Control Node

The onboarding process helps to establish a password-less connection between the Cloud Connect node and the Windows nodes. To onboard the Windows-based nodes to Orchestration control node, perform the following steps:

Procedure
Step 1

Configure SSH public key on the Windows nodes by following the steps in the Configure the SSH Public Key on Windows nodes section.

Step 2

Download the inventory to an SFTP server by running the utils system inventory export command. For details, see Export and Import of Nodes Managed by Orchestration Control Node.

Step 3

Edit the inventory to include Windows components.

  • The syntax, alignment, and indentation should be exactly as in the inventory file.

  • CRLF line endings should be of UNIX-Style. Hence a Linux-based or a Mac OS-based editor should be used to create the Windows inventory file.

  • The component names, such as CVPREPORTING, ROGGER, PG, and so on, must be in upper case.
Step 4

Import the inventory back from the SFTP server by running the utils system inventory import command on the Cloud Connect publisher node. For details, see Export and Import of Nodes Managed by Orchestration Control Node.

Add Deployment Type and Deployment Name

An administrator can edit the inventory file to add the details of the deployment.
Procedure
Step 1

Download the inventory to an SFTP server by running the utils system inventory export command. For details, see Export and Import of Nodes Managed by Orchestration Control Node.

Step 2

Edit the following strings in the inventory file, if required.

  • deploymentType: This field is used for compatibility check during an upgrade or rollback or switch forward procedure. The supported deployment types are:

    • UCCE-2000-Agents

    • UCCE-4000-Agents

    • UCCE-12000-Agents

    • UCCE-24000-Agents

    • PCCE-2000-Agents

    • PCCE-4000-Agents

    • PCCE-12000-Agents

    • HCS-CC-2000-Agents

    • HCS-CC-4000-Agents

    • HCS-CC-12000-Agents

    • HCS-CC-24000-Agents

    Note 

    For UCCE or HCS-CC 36000 Agents deployment, Use UCCE-24000-Agents or HCS-CC-24000-Agents as deployment type in the inventory.
    Note 

    HCS-SCC (Small Contact Center ) deployment model is currently not supported for Orchestration.

    Ensure that the values entered in this field conform to the above format. The deployment type is case sensitive..

  • deploymentName: Provide a unique name for the deployment.

    This name appears in the subject line of the email notification. If it is not configured, the subject line of the email notification contains only the type of procedure and the overall status.
Note 

The administrator can update or edit the default values, if required, based on their deployment type and preferred deployment name.

Step 3

Import the inventory back from the SFTP server by running the utils system inventory import command on the Cloud Connect publisher node. For details, see Export and Import of Nodes Managed by Orchestration Control Node.

Validate Onboarded Nodes for Orchestration

To validate the onboarding of VOS and Windows nodes, and to check whether the Orchestration feature is ready to be used, run the utils deployment test-connection command.

Command utils deployment test-connection
Description This command is used to validate whether password-less SSH connection is successful between the onboarded nodes and the Cloud Connect server. You can test the connection to all nodes on the deployment or to a specific group or individual nodes.
Expected Inputs NA
Expected Outcome Shows whether the inventory is accurate and the Cloud Connect node is able to connect to the managed hosts.

Configure HTTP Proxy Settings

If the Cloud Connect server requires an HTTP proxy server to check and fetch updates from the Cisco hosted cloud artifactory, configure the HTTP proxy with these steps:

Procedure
Step 1

Open a browser and type the following Cloud Connect URL: https://<CloudConnectIP>:8845/cloudconnectmgmt/config
Step 2

Provide your Cloud Connect application username or CLI Admin credentials. Upon successful authentication, you can make GET and PUT request to configure proxy for Cloud Connect server.

Step 3

Send a GET request to get the config.

Example:
GET the config
URL: https://<CloudConnectIP>:8845/cloudconnectmgmt/config
Method: GET
Step 4

Send a PUT request using any open source tools for API requests with proxyHost information to the same REST API in the payload. For example, set the proxyHost value to "proxy.dc.com" (this should be the actual FQDN proxy server name or IP address) and use the same value for lastUpdatedTimestamp received in GET API response. Upon successful execution of the PUT request, the Cloud Connect system will get updated with the proxy server information. To verify, repeat Step 1. Refer to the example below.

Example:
{
 
"CloudConnectMgmtConfig": {
 
"connCfg": {
 
"proxyEnabled": true,
 
"proxyHost": "proxy.dc.com",
 
"proxyPort": 80
 
},
 
"lastUpdatedTimestamp": 1559490732667
 
}
 
}

Configure Email Notification

When email notification is configured, the Cisco-hosted artifact repository is periodically checked for new software updates based on the default time for checking, and email notifications are sent. Release notes of new software updates are attached to the email notification.Aministrators can decide when to apply a patch or perform an upgrade. Email notifications are not triggered if no new software updates are available.


Note

The SMTP server referred to in this section is the mail server that is used within the customer organization for their internal email communication.

Perform the following procedures in the same sequence as given here.

1 Set up Email Notification
2 Validate Email Configuration
3 Subscribe for Email Notification
4 Configure Email Configuration
Set up Email Notification

Configure the email notification by running the following set of commands:

  • Set the IP address or hostname of the SMTP server by running the set smtp-host command.

    Command set smtp-host
    Description This command is used to set the IP address or hostname of the SMTP server.
    Expected Inputs SMTP server IP Address/HostName
    Expected Outcome The SMTP address is updated.

  • Set the email address from which emails are triggered by running the set smtp-from-email command.

    Command set smtp-from-email
    Description This command is used to set the email address from which the emails are triggered. This email address is not monitored and therefore not used for replying to any emails.
    Expected Inputs When executed, this command takes an input for an Email address.
    Expected Outcome Configures the email address from which email notifications are triggered.

  • Enable or disable SMTP authentication by running the set smtp-use-auth command.

    Command set smtp-use-auth
    Description This command is used to enable or disable SMTP authentication. By default, this is disabled.
    Expected Inputs The command takes an input for Enable or Disable.
    Expected Outcome SMTP authentication type is updated.

  • Set the username to be used for SMTP server connection by running the set smtp-user command. This is an optional configuration that needs to be set only when the SMTP authentication is enabled.

    Command set smtp-user
    Description This command is used to set the username to be used for SMTP server connection.
    Expected Inputs The command takes an input for a Username (username to be used for SMTP authentication)
    Expected Outcome Configures the SMTP username.

  • Set the password for SMTP server connection by running the set smtp-pswd command. This is an optional configuration that needs to be set only when the SMTP authentication is enabled.

    Command set smtp-pswd
    Description This command is used to set the password for SMTP server connection. The password is stored in an encrypted format. To change the password, run this command again.
    Expected Inputs The command prompts for a Password.
    Expected Outcome Configures the SMTP password.
Validate Email Configuration

Validate the configuration by running the utils smtp test-connection command.

Command utils smtp test-connection
Description This command is used to establish a connection to the SMTP server using the given configuration.
Expected Inputs NA
Expected Outcome Shows whether SMTP connection is successful or not.
Subscribe for Email Notification

Subscribe the administrator email address for email notification by running the utils smtp subscribe command.

Command utils smtp subscribe
Description This command is used to subscribe one or more email addresses for email notification. For example: 
utils smtp subscribe
 <emailaddress1,emailaddress2,.....emailaddressesN>
Expected Inputs Comma-separated list of valid email addresses to subscribe.
Expected Outcome Email addresses provided are subscribed for notification.

Configure Windows Server for Updates (Optional)

Microsoft Windows update configuration needs to be done on the target Windows node. Microsoft Windows updates can be downloaded in one of following ways on the target Windows node:

Administration Tasks


Note

Before upgrade or rollback of nodes managed by Orchestration, make sure to take backup as suggested by respective component documentation. Backup has to be done manually.


Note

In case the upgrade or rollback on VOS node fails, then the respective VOS node restart is mandatory before attempting the next upgrade or rollback on the same node. If the administrator does not restart, the next attempt to upgrade or rollback might fail.

Check Installed Software Version and Patches

To check the currently installed software version and patches on a node or group of nodes or all nodes in either Windows or VOS systems, run the utils deployment show status command.

Command utils deployment show status
Description This command is used to check the currently installed software version and patches for the selected Windows or VOS node individually or group of nodes or for all nodes in the inventory by selecting the option 'All Nodes in the inventory'.
Expected Inputs Select the node or group of nodes or all nodes from the inventory.
Expected Outcome Displays information about the installed software version and the patches for the selected node or group of nodes or all nodes from the inventory. If there is no patch installed, a message "No patch installed" is displayed to indicate that along with software version.

Install or Rollback Patch for Cloud Connect Server

To install a patch or to roll back a previously installed patch on Cloud Connect server, run the utils system upgrade initiate command. The Local Repository option in this command lists the patches available from Cisco artifactory for installation or rollback on Cloud Connect server. This command can be run separately on the Cloud Connect publisher and subscriber nodes.


Note

The Local Repository option is also available on the Cisco Unified OS Administration web page of Cloud Connect server. Select this option to install a patch or to roll back a previously installed patch on Cloud Connect server.


Note

The Local Repository in utils system upgrade initiate command will support upgrade from 12.6 version to next version in future.

Command utils system upgrade initiate
Description This command is used to initiate the patch install or to roll back the previously installed patch on Cloud Connect server. The patches available for installation and rollback are listed from Cisco artifactory.
Expected Inputs Select the Local Repository option to list the patches available for installation or rollback.

Select the patch to install or roll back.

Expected Outcome The selected patch for install or rollback is installed on Cloud Connect server.

Note

The Local Repository option is used only after the Cisco Artifactory is successfully configured on Cloud Connect server. See CLI to configure Artifactory URL and API Key for configuring Cisco artifactory.


Note

Optionally, to receive email notification about the status of the patch installation or rollback for Cloud Connect server, provide the SMTP host server details when prompted by the CLI.


Note

Patch install or roll back on Cloud Connect server initiated using utils system upgrade initiate command can be canceled using utils system upgrade cancel command. The utils system upgrade status command can be used to check the status.

List Available Patches for Specific Node or Group of Nodes

To get a list of available patches for a specific node or group of nodes in the inventory, run the utils patch-manager list command.

Command utils patch-manager list
Description This command is used to get a list of patches available for installation for a specific node or group of nodes based on the selected option.
Expected Inputs Select a node or group of nodes based on the inventory.
Expected Outcome Displays information about available patches for the selected node or group of nodes.

Note

You can check the status of the system maintenance initiate, patch install, patch rollback, upgrade, rollback, or switch forward which is currently in-progress. If there is no system maintenance initiate, patch install, patch rollback, upgrade, rollback, or switch forward in progress, you can see the status of the previously completed operation. See Check Status.

Install Patch to Specific Node or Group of Nodes

To install patch to a specific node or group of nodes, run the utils patch-manager install command.

Command utils patch-manager install
Description This command is used to install patches on a specific node or group of nodes onboarded to the Cloud Connect inventory.
Expected Inputs From the list of Windows/VOS nodes displayed, select the node or group of Windows/VOS nodes on which the patch needs to be installed. Once you select the nodes, only the nodes for which patches are available will be displayed. For example, if you select 3 nodes and Windows/VOS patches are available for only 1 of them, you are asked to proceed with only one node. Confirm to proceed. You are also asked to confirm whether the target node needs to be rebooted after installing the patch.

Selection of components such as Finesse, CVP Call Server, IdS, and PG with software version 12.6.1 and above will provide the options "With maintenance mode” and “Without maintenance mode”..

If you select a group of nodes with some nodes on 12.6.1 and above and some nodes on below 12.6.1, then "With maintenance mode” or “Without maintenance mode” option will not be available. In this case if "With maintenance mode” option is required, then the individual node with 12.6.1 and above can be selected separately.

If you select “With maintenance mode” option, the maintenance mode is initiated for the selected node to failover active traffic gracefully or shutdown the services gracefully without interrupting the active traffic or causing outage for new traffic before installing the patch and automatically rebooting. If you select, “Without maintenance mode” option, you are initially asked to confirm to proceed. Next, you are asked to provide confirmation on rebooting the node after installing the patch
Expected Outcome The selected patch is installed on the selected node or group of nodes.

Note

To start ICM services, post the successful completion of patch install with reboot on ICM nodes. See Start ICM Services.

Note

Maintenance mode for IDS co-resident in 2000 Agents Deployment model is not supported

Roll Back Patch from Specific Node or Group of Nodes

To roll back a previously installed patch on a specific node or a group of nodes, run the utils patch-manager rollback command.

Command utils patch-manager rollback
Description This command is used to roll back previously installed patches on a specific node or group of nodes.

In case of Windows-based nodes, the latest applied patch is allowed to roll back. In case of VOS-based nodes, the latest applied COP is rolled back.

Expected Inputs From the list of Windows/VOS nodes displayed, select the node or group of Windows/VOS nodes on which the patch needs to be rolled back. Once you select the nodes, only the nodes for which Windows/VOS patch rollback is available will be displayed. For example, if you select 3 nodes and Windows/VOS patch rollback is available for only 1 of them, you are asked to proceed with only one node. There is also a message displayed indicating that the machine would restart after the patch is rolled back. Confirm to proceed.

Selection of components such as Finesse, CVP Call Server, IdS, and PG with software version 12.6.1 and above will provide the options "With maintenance mode” and “Without maintenance mode”.

If you select a group of nodes with some nodes on 12.6.1 and above and some nodes on below 12.6.1, then "With maintenance mode” or “Without maintenance mode” option will not be available. In this case if "With maintenance mode” option is required, then the individual node with 12.6.1 and above can be selected separately.

If you select “With maintenance mode” option, the maintenance mode is initiated for the selected node to failover active traffic gracefully or shutdown the services gracefully without interrupting the active traffic or causing outage for new traffic before rollback and automatically rebooting. If you select, “Without maintenance mode” option, you are initially asked to confirm to proceed. Next, you are asked to provide confirmation on rebooting the node after rollback.

Expected Outcome The previously installed patch is rolled back on the selected node or group of nodes.

Note

To start ICM services, post the successful completion of patch roll back with reboot on ICM nodes. See Start ICM Services

Install Windows Updates to Specific Node or Group of Nodes

To install Windows updates to a node or group of nodes or all Windows nodes, run the utils patch-manager ms-patches install command.


Note
Command utils patch-manager ms-patches install
Description This command is used to install the latest Windows updates to a node or a group of Windows nodes or all Windows nodes.
Expected Inputs From the list of Windows nodes displayed, select the node or group of Windows nodes or all Windows nodes to which the updates need to be applied. You can also select all the Windows nodes in the inventory. Once you select the nodes, only the nodes for which Windows updates are available will be displayed. For example, if you select 3 nodes and Windows updates are available for only 1 of them, you are asked to proceed with only one node. Confirm to proceed. You are asked to confirm whether the target nodes needs to be rebooted after installing the updates.

Selection of components such as CVP Call Server and PG with software version 12.6.1 and above will provide the options "With maintenance mode” and “Without maintenance mode”.

If you select a group of nodes with some nodes on 12.6.1 and above and some nodes on below 12.6.1, then "With maintenance mode” or “Without maintenance mode” option will not be available. In this case if "With maintenance mode” option is required, then the individual node with 12.6.1 and above can be selected separately.

If you select “With maintenance mode” option, the maintenance mode is initiated for the selected node to failover active traffic gracefully or shutdown the services gracefully without interrupting the active traffic or causing outage for new traffic before installing the update and automatically rebooting. If you select, “Without maintenance mode” option, you are initially asked to confirm to proceed. Next, you are asked to provide confirmation on rebooting the node after installing the patch.

Expected Outcome The selected Windows updates are installed on the selected node or group of nodes or all Windows nodes.

Roll Back Windows Update from Specific Node or Group of Nodes

To roll back Windows update from a specific node or group of nodes or all Windows nodes, run the utils patch-manager ms-patches rollback command.


Note
Command utils patch-manager ms-patches rollback
Description This command is used to roll back a specific Windows update from a specific node or group of nodes or all Windows nodes.
Expected Inputs Select the node or group of Windows nodes or all Windows nodes on which the rollback needs to be performed. You can also select all the Windows nodes in the inventory for rollback. Provide the KB number you want to rollback. Confirm whether the target node can be rebooted after the rollback.

Selection of components such as CVP Call Server and PG with software version 12.6.1 and above will provide the options "With maintenance mode” and “Without maintenance mode”.

If you select a group of nodes with some nodes on 12.6.1 and above and some nodes on below 12.6.1, then "With maintenance mode” or “Without maintenance mode” option will not be available. In this case if "With maintenance mode” option is required, then the individual node with 12.6.1 and above can be selected separately.

If you select “With maintenance mode” option, the maintenance mode is initiated for the selected node to failover active traffic gracefully or shutdown the services gracefully without interrupting the active traffic or causing outage for new traffic after rollback and automatically rebooting. If you select, “Without maintenance mode” option, you are initially asked to confirm to proceed. Next, you are asked to provide confirmation on rebooting the node after rollback.

Expected Outcome The selected Windows updates are rolled back.

Enable or Disable Compatibility Enforcement

You can enable or disable compatibility enforcement. When the compatibility enforcement is enabled, it ensures that the upgrade, rollback, or switch forward is as per the compatibility matrix published by Cisco for reference design-based deployment. To enable or disable compatibility enforcement, run the utils deployment compatibility-check command.


Note

By default, the compatibility enforcement is enabled.

When the compatibility enforcement is disabled, the Orchestration framework does not enforce upgrade, rollback, or switch forward as per the compatibility matrix published by Cisco.

Command utils deployment compatibility-check
Description This command is used to enable or disable compatibility enforcement.
Expected Inputs User confirmation to proceed with enabling or disabling compatibility enforcement.
Expected Outcome Message about the success or failure of enabling or disabling compatibility enforcement.

Note

You can run this command only from the publisher node of the Cloud Connect server. The compatibility configuration replicates automatically from the publisher node to the subscriber node when the utils deployment compatibility-check command is run with successful results on the publisher node.

Initiate maintenance mode for a specific node

Initiating maintenance mode allows the components to failover gracefully or shutdown the services gracefully (depending on the selected components) without interrupting the active traffic or causing outage to new traffic. This ensures that the system can be taken down for maintenance activity such as installing new software updates, restarting services etc. Currently, maintenance mode is supported for PG, CVP server, IdS, and Finesse. Ensure that not all CVP servers are put into maintenance mode at same time, so that incoming call traffic can be distributed.

To initiate maintenance mode for a specific node in the inventory, run the utils system maintenance initiate command.

Command utils system maintenance initiate
Description This command is used to initiate maintenance mode for a specific node based on the selected option. Currently, the initiate maintenance command is available for Finesse, CVP Call Server, IdS, and PG components.
Expected Inputs When executed, this command prompts you to select a node based on the inventory.
Expected Outcome Information about success or failure of the initiate maintenance command for a selected node is displayed.

Note

The utils system maintenance initiate is applicable for target nodes on 12.6(1).


Note

If either the Publisher or Subcriber or the active/inactive node is already in maintenance mode in any of the components, the other server cannot be initiated for maintenance.


Note

Maintenance mode for IDS co-resident in 2000 Agents Deployment model is not supported

List Available Upgrade Options

To get a list of available upgrade options for VOS and Windows nodes individually or for group of nodes or for all nodes in the inventory, run the utils upgrade-manager list command.

Command utils upgrade-manager list
Description This command is used to get a list of upgrade options available for the selected VOS or Windows node or group of nodes or all nodes in the inventory by selecting the option "All nodes in the inventory"..
Expected Inputs Select a node or group of nodes or all nodes based on the inventory.
Expected Outcome Displays information about available upgrade options for selected VOS or Windows nodes or group of nodes or all nodes in the inventory.

If the selected node or group of nodes or all nodes are already running the latest software version, a message is displayed to indicate that.

Upgrade a Specific Node or Group of Nodes or All Nodes

To perform software version upgrades on VOS or Windows nodes or All nodes in the deployment (VOS and Windows nodes together), run the utils upgrade-manager upgrade command from the Cloud Connect server. It is recommended to run this command during a maintenance window as the procedure involves system restart that will cause service outage.

For the selected VOS or Windows component for upgrade, a compatibility check is performed in the background based on the configured deployment type to ensure that all the associated components are onboarded. If the components are onboarded and the required dependent components are either in same target upgrade version or backward compatible version, the upgrade procedure begins. However, if the components are not onboarded, you have to onboard them first or if the versions are not compatible, upgrade them to the required version. For example, if you select to upgrade the Rogger nodes to 12.6.1 version, the inter-component compatibility check is run for the Rogger dependent components such as Finesse, CVP, VVB, CUIC. These must already be in 12.6 version and PG must be backward compatible version, that is, 12.5.1 .


Note

The sub-components sequence dependencies are not validated as part of the upgrade compatibility. Refer to the upgrade guides of the respective components for the correct sequence. For example, in case of CVP, we have sub-components such as Operations Console, Unified CVP Reporting Server and Unified CVP Server. These must be upgraded in the required sequence.

For VOS node/cluster, switch forward is optional at the end of upgrade. If administrators opt for switch forward, the target node is restarted and the active/inactive partition is switched. If they decide not to switch forward, the upgraded version remains in the inactive partition of the target node. Switch forward for these nodes can be performed later. For details, see Perform Switch Forward on Specific VOS Node or Group of Nodes.

For VOS cluster, the upgrade or the switch forward procedure is performed first on the publisher and then on the subscriber nodes. If switch forward is performed immediately after an upgrade, the overall procedure takes a significant amount of time; hence plan the maintenance window accordingly.

For selecting "All nodes" option during upgrade, make sure that all the VOS and Windows nodes onboarded are on the same software version. Stage-wise upgrade is performed for the solution components as per the CCE Installation and Upgrade guide. In case of any component upgrade failure during execution, the upgrade does not proceed to the next stage. The administrator has to upgrade individual components by selecting the respective individual VOS or Windows nodes.

Command utils upgrade-manager upgrade
Description This command is used to upgrade VOS or Windows nodes or group of nodes or All nodes in the deployment (VOS and Windows nodes together) in the inventory.
Expected Inputs Select the Windows or VOS node or group of nodes or all nodes in the deployment (VOS and Windows nodes together) that you want to upgrade.

From the list of upgrade options available for the selected node or group of nodes or all nodes, select the appropriate option and confirm. A compatibility check is then run in the background.

To select "All nodes" upgrade option, make sure that all the VOS and Windows nodes onboarded and the components are on the same software version.

Once the upgrade procedure begins, you can see the progress details for each of the machines. You can also see the elapsed time since the procedure started.

Expected Outcome The selected node or group of nodes or all nodes is upgraded.

Note

  • For faster upgrades, the Cloud Connect server downloads locally all the new software updates from the Cisco hosted repository at a predefined time.

  • To start ICM services, post the successful completion of upgrade with reboot on ICM nodes. See Start ICM Services

Perform Switch Forward on Specific VOS Node or Group of Nodes

Administrators can perform switch forward on target VOS nodes independently. When the active partition is on lower version and the inactive partition is on higher version, run the utils upgrade-manager switch-forward command to perform a switch forward. It is recommended to run this command during a maintenance window as the procedure involves system restart that will cause service outage.

Command utils upgrade-manager switch-forward
Description This command is used to switch forward on target VOS node/cluster from Cloud Connect server.
Expected Inputs Select the VOS node/cluster on which you want to perform the switch forward. You will see the details of the current active/inactive versions. Confirm to proceed with the switch forward.

A compatibility check is then run in the background.

  • If there are components whose versions are not compatible or the components are not onboarded as per the compatibility requirements, a list of those components is displayed. Upgrade or switch forward the listed components to the required software versions and re-run this command.

  • If the versions of the associated components are compatible with the node’s inactive version, then the switch forward procedure continues.

Once the switch-forward procedure begins, you can see the progress details for each of the machines. You can also see the elapsed time since the procedure started.

Expected Outcome The system restarts and the current version of the system is on a higher version.

Roll Back Upgrade from Specific Node or Group of Nodes

To roll back an upgrade on VOS or Windows nodes, run the utils upgrade-manager rollback command from the Cloud Connect server. It is recommended to run this command during a maintenance window as the procedure involves system restart that will cause service outage.

For the selected VOS or Windows component for rollback, a compatibility check is performed in the background to ensure that all the associated components are onboarded and the versions are compatible. If the components are onboarded and the versions are compatible with each other, the rollback procedure begins. However, if the components are not onboarded, you have to onboard them first or if the versions are not compatible, roll them back to the required version.

For VOS nodes/cluster, the rollback (switch backward) must be initiated from an active higher version to an inactive lower version of the node. Also, the publisher node of the managed cluster must be rolled back before the subscriber node of the cluster.

Command utils upgrade-manager rollback
Description This command is used to roll back an upgrade on VOS or Windows nodes.
Expected Inputs Select the Windows node or VOS node/cluster on which you want to perform the rollback. The rollback option is listed for the selected node or group of nodes. Select the appropriate option and confirm. A compatibility check is then run in the background.

  • If there are components whose versions are not compatible or if the components are not onboarded as per the compatibility requirements, a list of these components is displayed. Roll back the listed components to the required software versions and then re-run this command.

  • If the versions of the associated components are compatible with the selected node's rollback version, then the rollback procedure begins.

Once the rollback procedure begins, you can see the progress details for each of the machines. You can also see the elapsed time since the procedure started.
Expected Outcome The selected node or group of nodes is rolled back.

Note

To start ICM services, post the successful completion of roll back upgrade with reboot on ICM nodes. See Start ICM Services

Check Status

To check the current status of patch manager install, patch manager rollback, upgrade manager upgrade, upgrade manager rollback, switch-forward, or system maintenance initiate initiate run the utils deployment show in-progress command. You can run this command if connectivity to CLI is lost after initiating any of above procedures.

Command utils deployment show in-progress
Description This command is used to check the current status of any patch manager install, patch manager rollback, upgrade manager upgrade, upgrade manager rollback, switch-forward or system maintenance initiate. It also shows the subsequent progress, if applicable, for each node on which the procedure is initiated.

If there is no procedure in progress, this command gives the last successful/failed execution status.

Expected Inputs NA
Expected Outcome Shows the current status of the patch manager install, patch manager rollback, upgrade manager upgrade, upgrade manager rollback, switch-forwardor system maintenance initiate for each node.

If there is no patch manager install, patch manager rollback, upgrade manager upgrade, upgrade manager rollback, switch-forward, or system maintenance initiate, then you see the status of the previous upgrade, rollback, or maintenance.

Check Last Known Orchestration Operation Status on Remote Node

To check the last known orchestration operation status (last completed state or last known state when the operation is in progress or when the remote node is not reachable ) on the remote node, run the utils deployment show progress-HA command. This command is applicable for patch manager install, patch manager rollback, upgrade manager upgrade, upgrade manager rollback, ms patch install, ms patch rollback, switch-forward, system maintenance initiate, and ICM services start.

This command can be used only in Cloud Connect High Availability setup

Command utils deployment show progress-HA
Description This command is used to check the last known operation status run on remote node. This will only display the snapshot of the last known operation status and will not display the continuous status changes for the operation that is currently in progress. This command can be used to check the last known operation status on the remote node when the Cloud Connect node is not reachable.
Expected Inputs NA
Expected Outcome

The snapshot of the last known operation status is displayed.

Note

Last known orchestration operation status will not be synchronized to remote node, in case of communication loss to remote node after initiating the orchestration operation and operation being completed before re-establishing the communication.

Start ICM Services

To start ICM services from Cloud Connect server, run the utils system icm-services start command.

Command utils system icm-services start
Description This command is used to start the ICM services from Cloud Connect server. This CLI will present the user with a list of ICM hosts configured in the inventory, and the admin can select individual or group of ICM hosts.
Expected Inputs

User should choose individual or group of ICM hosts from the list.

User should give confirmation yes/no to proceed with start of ICM services
Expected Outcome As part of CLI output, there are two kinds of messages which displays success as shown below:

  • When the ICM services are started successfully from stop state, the message “Services started” is displayed.

  • When the ICM services are already up and running, the message “Services running” is displayed.

Maintenance Tasks

Update VOS Nodes Onboarded to Orchestration Control Node

To update VOS based nodes that have been onboarded, run the utils system onboard update command from the publisher node in the VOS node/cluster that you want to update.

Command utils system onboard update
Description This command is used to update a node/cluster on a Cloud Connect node.
Expected Inputs When executed, this command prompts for:

  • Cloud Connect server FQDN

  • Cloud Connect application username and password
Expected Outcome The existing node/cluster is updated in the Cloud Connect node inventory.

Remove VOS Nodes from Orchestration Control Node

To remove any existing VOS-based node or cluster, run the utils system onboard remove command from the publisher node in the VOS node/cluster that you want to remove.

Command utils system onboard remove
Description This command is used to remove a node/cluster from a Cloud Connect node.
Expected Inputs When executed, this command prompts for:

  • Cloud Connect server FQDN

  • Cloud Connect application username and password
Expected Outcome The node/cluster is successfully removed from the Cloud Connect node inventory.

Update Windows Nodes Onboarded to Orchestration Control Node

The update procedure is similar to the onboarding procedure described in Onboard Windows Nodes to Orchestration Control Node.


Note

If SSH connection is already established, skip Step 1 in the above procedure.

Configure Email Configuration

You can check your email configuration details by running the respective commands as described below:

  • Get the IP address and hostname of the SMTP server by running the show smtp-host command.

    Command show smtp-host
    Description This command is used to get the IP address or hostname of the SMTP server.
    Expected Inputs NA
    Expected Outcome Shows the configured IP address or host name of the SMTP server.

  • Get the email address from which the emails are triggered by running the show smtp-from-email command.

    Command show smtp-from-email
    Description This command is used to get the email address from which the emails are triggered. This email address is not monitored and therefore not used for replying to any emails.
    Expected Inputs NA
    Expected Outcome Shows the email address from which the emails are triggered.

  • See if SMTP authentication is enabled or not by running the show smtp-use-auth command.

    Command show smtp-use-auth
    Description This command is used to know if SMTP authentication is enabled or not.
    Expected Inputs NA
    Expected Outcome SMTP authentication : <enable/disable>

  • Get the username for SMTP server connection by running the show smtp-user command.

    Command show smtp-user
    Description This command is used to show the user name to be used for SMTP server connection.
    Expected Inputs NA
    Expected Outcome Shows the SMTP username.

  • See if the SMTP password is set or not by running the show smtp-pswd command.

    Command show smtp-pswd
    Description This command is used to know if the SMTP password is set or not. To reset the password, run the set smtp-pswd command.
    Expected Inputs NA
    Expected Outcome Shows whether the SMTP password is set or not.

  • See the email addresses subscribed for notification by running the utils smtp show subscriptions command.

    Command utils smtp show subscriptions
    Description This command is used to get a list of all the email addresses subscribed for email notification.
    Expected Inputs NA
    Expected Outcome Shows the email addresses that are subscribed for email notification.

    If there is no email address subscribed, a message is displayed indicating it.

Delete Configuration for Email Notification

To remove the configuration for email notifications, run the utils smtp remove-config command.

Command utils smtp remove-config
Description This command is used to remove the SMTP configuration from the control node. Email notification will no longer be sent to the subscribed email addresses. This command removes only the SMTP configuration, not the subscribed email addresses.
Expected Inputs NA
Expected Outcome SMTP configuration is deleted.

Unsubscribe Email Notification

To unsubscribe from email notifications, run the utils smtp unsubscribe command.

Command utils smtp unsubscribe
Description This command is used to remove one or more email addresses from the existing list of subscribers for email notification.
Note 

You can get a list of subscribed email addresses using the utils smtp show subscriptions command.

Expected Inputs Provide a comma-separated list of the email addresses to unsubscribe. For example:

utils smtp unsubscribe <emailaddress1,emailaddress2,.....emailaddressesN>

You can also remove all the subscribed email addresses from the subscription list at once. To do that, run utils smtp unsubscribe all and confirm.

Expected Outcome Removes the email addresses you provided as the input from the subscription list.

Export and Import of Nodes Managed by Orchestration Control Node

To export inventory to an SFTP server, run the utils system inventory export command.

Command utils system inventory export
Description This command is used to export inventory to an SFTP server location. The inventory file can then be viewed and edited as required.
Expected Inputs When executed, this command prompts for:

  • SFTP Server: IP address of the SFTP remote server

  • SFTP User

  • SFTP User's Password

  • SFTP Directory: Location of the remote server directory where the inventory needs to be exported

    Note 

    Provide the location only; the filename is inventory.conf by default.

Expected Outcome Inventory is exported to the SFTP server location.

To import inventory to Cloud Connect server, run the utils system inventory import command.

Command utils system inventory import
Description This command is used to import inventory to Cloud Connect server.
Expected Inputs When executed, this command prompts for:

  • SFTP Server: IP address of the SFTP remote server

  • SFTP User

  • SFTP User's Password

  • SFTP Directory: Location of the remote server directory from where the inventory needs to be imported

    Note 

    • Provide the location only. The filename is inventory.conf by default.

    • During inventory import, the inventory.conf filename should have the side information added for each node. For example, side: "A" /side: "B". During inventory import, the cluster information cannot be blank. It should have valid host details or a default value {}. For example, "ROGGER":{}

Expected Outcome Inventory is imported to Cloud Connect server.

Note

For information on adding deployment type and deployment name in the inventory file, see Add Deployment Type and Deployment Name.

Export Current Patch Level Details

Available patches for nodes in the deployment can be obtained in either of the following ways:

  • Email Notification

  • Using the utils patch-manager list command.

Current patch levels can be exported in text file format using the utils patch-manager export status command.

Command utils patch-manager export status
Description This command is used to export the patch level details of a node or a group of nodes in a text file format.
Expected Inputs Select the node(s) and enter the SFTP server details.
Expected Outcome A text file with the current patch levels of the selected nodes is exported to the provided location. A success message is displayed along with the location where the file is saved.

Serviceability

Audit Logs

Audit trial for administrative operation that is initiated from Orchestration CLI on Cloud Connect is captured in Orchestration Audit logs. Audit trial captures the user, action and date/time details of the CLI operation.

  • file get activelog orchestration-audit/audit.log*

CLI Logs

Run the following command on the Cloud Connect node to retrieve CLI logs:

  • file get activelog platform/log/cli*.log

Ansible Logs

Run the following commands on the Cloud Connect node to retrieve ansible-related logs:

  • Current transaction logs: file get activelog ansible/ansible.log

  • Historical logs: file get activelog ansible/ansible_history.log

Operation Status HA Synchronization Logs

Run the following command on the Cloud Connect node to retrieve synchronization-related logs:

  • file get activelog ansible/sync_ansible_log_to_remote_cc.log

Email Notification-related Logs

Run the following commands on the Cloud Connect node to retrieve email-related logs:

  • Current transaction logs:file get activelog ansible/ansible_email_cron.log

Software Download Logs

Run the following commands on the Cloud Connect node to retrieve software download-related logs:

  • Current transaction logs:file get activelog ansible/software_download_ansible.log

  • Historical logs:file get activelog ansible/software_download_ansible_history.log

  • Process logs:file get activelog ansible/software_download_process.log


Note

Software is downloaded separately on Cloud Connect publisher and subscriber.

Orchestration Logs in RTMT

You can also view the below-mentioned logs using the Real-Time Monitoring Tool (RTMT):

  • Ansible logs by selecting 'Ansible Controller' as the service

  • Audit logs by selecting 'Orchestration Audit' as the service

To download RTMT from Cloud Connect, access https://FQDN:8443/plugins/CcmServRtmtPlugin.exe.

For more information, refer to the Cisco Unified Real-Time Monitoring Tool Administration Guide at:https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-maintenance-guides-list.html.

For logs on individual components, refer to the Serviceability Guide for Cisco Unified ICM/Contact Center Enterprise available at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-enterprise/products-installation-and-configuration-guides-list.html.

Enable and View Windows Open SSH Logs

To enable and view open SSH logs, do the following:

  • Make sure the sshd_config file %programdata%\ssh\sshd_config has the value as 'LogLevel DEBUG' and uncomment the line.

  • Restart the service (select service name OpenSSH SSH Server).

  • In the Windows Event Viewer, select option Show Analytic and Debug Logs from View on the top menu bar.

  • Select Debug channel from OpenSSH folder.

  • On the right hand side, under Actions from Debug channel, select Enable log.

To turn on file-based logging, do the following:

  • In the sshd_config file %programdata%\ssh\sshd_config, set the value as "SyslogFacility LOCAL0" and uncomment the line.

  • Restart the service (select service name OpenSSH SSH Server).

  • The file based logs are collected at location %programdata%\ssh\logs.

Configure the SSH Public Key on Windows nodes

This section describes how to establish password-less Secure Shell (SSH) connection between Cloud Connect server and Windows node (CVP and ICM) using SSH public key. The Windows node can be in a Workgroup or Domain.


Note

If the Windows node (CVP and ICM) version is 12.5, install 12.5 mandatory ES before performing this procedure. See System Requirements for 12.5 mandatory ES details.

  1. Navigate to %Users%\<logonUser>\.ssh\ and create authorized_keys file, if it does not exist.


    Note

    The authorized_keys extension type is File and should not be modified.

  2. Open the browser and enter the following Cloud Connect publisher URL: https://<CloudConnectIP>:8445/inventory/controlnode/key

  3. Provide your Cloud Connect application username or CLI Admin credentials. Upon successful authentication, a REST API response fetches the Cloud Connect Public SSH Key.

  4. Copy this public key value into the authorized_keys file in %Users%\<logonUser>\.ssh\.

  5. Repeat steps 2, 3, and 4 to fetch the Cloud Connect subscriber public key (if Cloud Connect is HA setup).


    Note

    Cloud Connect publisher and subscriber public keys should be copied into a single authorized_keys file. The publisher and subscriber entries should be in separate lines and should not use any extra space, comma, or any special characters at the end of the line.

  6. Restart the following OpenSSH services:

    • OpenSSH SSH Server

    • OpenSSH Authentication Agent


Note

For more information on Windows security hardening, see UCCE Security Guide at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-enterprise/products-installation-and-configuration-guides-list.html.

Self-Signed Certificate

You must import the self-signed certificates of both Cloud Connect publisher and subscriber nodes to the VOS publisher and subscriber nodes.

Get Tomcat Certificate from Cloud Connect Server

Procedure

Step 1

Login to the Cloud Connect server using: https://<cloud connect hostname>:8443/cmplatform.

Step 2

Navigate to Security > Certificate Management.

Step 3

Click Find.

Step 4

Click on the Tomcat certificate of the Cloud Connect server.
Step 5

Download the .PEM file and save the file.

Import Cloud Connect Server Tomcat Certificate to VOS Nodes

Procedure

Step 1

Login to the VOS node server using: https://<VOS node hostname>:8443/cmplatform.

Step 2

Navigate to Security > Certificate Management.

Step 3

Click on Upload Certificate/Certificate Chain.
Step 4

Select ‘tomcat-trust’ from the drop-down list in the Certificate Purpose field.

Step 5

Click Browse to upload the Cloud Connect server .PEM file.

Step 6

Click Upload.

Step 7

Restart the specific VOS node by running the utils system restart command.

Things to Know

  • Orchestration is not supported for Customer Collaboration Platform (CCP), ECE, CCDM, CCMP, and non-Contact Center Cisco products such as UCM, Unity Connection, CUBE gateways, CUSP, IM&P etc. Patches and upgrade operations for these components can be performed in a traditional manner.

  • In higher deployment like 24000 Agents or 36000 Agents, if maximum number of nodes has to be selected at once for upgrade in non-production environment, We recommend to use All nodes options in utils upgrade-manager upgrade and utils upgrade-manager list commands instead of selecting the group of Windows or VOS nodes.

  • Orchestration is supported only for upgrades and patch install and not for tech refresh or fresh install.

  • If any activity is blocked with a message previous orchestration or upgrade operation is still in progress even if there is no active operation, then restart Cloud Connect server.

  • If one component ES has a dependency on another component ES, then they have to be taken into consideration by the administrator before initiating the patch installation from Cloud Connect server. The administrator should read the release notes that is notified through an email to understand the dependency. The Orchestration framework does not track this aspect automatically. For example, if an ES of Finesse has a dependency on an ES of Live Data and has to be installed in a specific order, then the administrator must consider this before initiating the patch installation from Cloud Connect server.

  • Within Upgrade commands 'All Nodes' option for the Roll Back and Switch version commands are not available.

  • Only Microsoft Exchange Server is supported for email notification; Office 365 and Gmail are not supported as of now.

  • Email notifications are triggered about the available software upgrade from the publisher node of Cloud Connect server. If the publisher node is down at the trigger time, then the Admin will not receive any notification.

  • All nodes option in utils upgrade-manager list CLI uses an internal cache, which is updated every day at 5 AM. The latest version of components that are upgraded before the cache update scheduled time will not be listed in All nodes option. The latest version of components can be listed by selecting the individual VOS or Windows or group of nodes option in the utils upgrade-manager list CLI. The cache update can be enforced by executing utils system inventory import CLI.

  • For PCCE deployment, only multistage upgrade is supported from Orchestration.

  • For PCCE deployment, CVPOAMP is not supported.