CISCO CCE-2000 Packaged Agent Deployment User Manual
File info: application/pdf · 20 pages · 4.92MB
Upgrade Overview
Extracted Text
Upgrade Overview Following are the two supported upgrade methods: � Common Ground Upgrades: The Common Ground method is an in-place upgrade performed on your existing virtual machine which involves upgrading the Packaged CCE and all other associated software hosted on it. If your hardware meets the requirements for this release, you can perform a Common Ground upgrade without acquiring additional hardware. Note � CCE components can be upgraded using common ground or technology refresh upgrade. � Common Ground Upgrade is not supported if the platform upgrade from Windows Server 2016 and SQL Server 2017 to Windows Server 2019 and SQL Server 2019 is planned as part of upgrade process. � Technology Refresh Upgrades: Use the Technology Refresh upgrade method to set up all the virtual machines (VMs) or the required set of VMs on a different hardware. You can also upgrade the solution components and the associated software hosted on it. Note For better performance, Media Routing PG (MR PG), Dialer, and Agent PG should be on the same VM. � Upgrade Flow, on page 1 � Silent Upgrade, on page 19 � Custom Truststore to Store Component Certificates, on page 19 Upgrade Flow Upgrade Flowcharts for 2000 Agent Deployments The following diagram illustrates the solution-level upgrade flow for the Packaged CCE 2000 Agent Deployment solution upgrade. Upgrade Overview 1 Upgrade Flowcharts for 2000 Agent Deployments Note This flowchart is not applicable for redundant upgrade workflow. Upgrade Overview The following diagrams illustrate the stages of the component-level upgrade flows for the Packaged CCE 2000 Agent Deployment solution upgrade. Each diagram covers one of the stages. The letter at the end of each flow indicates the start of the next flow that you are required to perform. Upgrade Overview 2 Upgrade Overview Upgrade Flowcharts for 2000 Agent Deployments Upgrade Overview 3 Upgrade Flowcharts for 2000 Agent Deployments Upgrade Overview Upgrade Overview 4 Upgrade Overview Upgrade Flowcharts for 2000 Agent Deployments Upgrade Overview 5 Upgrade Flowcharts for 2000 Agent Deployments Upgrade Overview Upgrade Overview 6 Upgrade Overview Upgrade Flowcharts for 2000 Agent Deployments Upgrade Overview 7 Upgrade Flowcharts for 2000 Agent Deployments Upgrade Overview Upgrade Overview 8 Upgrade Overview Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Flowcharts for 4000 Agents and above Deployments The following diagram illustrates the solution-level upgrade flow for the Packaged CCE 4000 Agents and above Deployment solution upgrade. Upgrade Overview 9 Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview The following diagrams illustrate the stages of the component-level upgrade flows for the Packaged CCE 4000 Agents and above Deployment solution upgrade. Each diagram covers one of the stages. The letter at the end of each flow indicates the start of the next flow that you are required to perform. Upgrade Overview 10 Upgrade Overview Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview 11 Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview Upgrade Overview 12 Upgrade Overview Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview 13 Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview Upgrade Overview 14 Upgrade Overview Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview 15 Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview Upgrade Overview 16 Upgrade Overview Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview 17 Upgrade Flowcharts for 4000 Agents and above Deployments Upgrade Overview Upgrade Overview 18 Upgrade Overview Silent Upgrade Silent Upgrade There are situations when silent upgrade can be used in running an installation wizard. You can run a silent installation while performing a fresh install or an upgrade. For more information, see Silent Installation. Custom Truststore to Store Component Certificates Starting Unified CCE 12.6(x), a new custom truststore is created under the Unified ICM Installation directory <ICM install directory>\ssl\cacerts to store all the component certificates. With this new custom truststore, you don't need to export and import the certificates each time Java is updated in the system. After upgrading from Unified CCE 12.5(x) to Unified CCE 12.6(x), you should export the certificates from the Java truststore to the custom truststore under the Unified ICM Installation directory <ICM install directory>\ssl\cacerts. Export the certificate from the Java truststore: Upgrade Overview 19 Custom Truststore to Store Component Certificates Upgrade Overview � Run the command at the command prompt: cd %JAVA_HOME%\bin. Important Use CCE_JAVA_HOME if upgrading from Unified CCE 12.5(1a) or Unified CCE 12.5(1) with ES55 (mandatory OpenJDK ES). � Export the certificates of all the components imported into the truststore. The command to export the certificates is keytool -export -keystore <JRE path>\lib\security\cacerts -alias <alias of the component> -file <filepath>.cer � Enter the truststore password when prompted. Import the certificate to the custom truststore: � Run the command at the command prompt: cd %CCE_JAVA_HOME%\bin. � Import the certificates for all the components that you exported from the Java truststore. The command to import certificates is keytool -import -keystore <ICM install directory>\ssl\cacerts -file <filepath>.cer -alias <alias>. � Enter the truststore password when prompted. � Enter 'yes' when prompted to trust the certificate. Upgrade Overview 20