Key tasks for upgrading Communication Manager to Release 10.2.x using SDM

Last Updated : Feb 10, 2022 |
Prolog information
The table contains the key tasks that are required to upgrade Communication Manager to Release 10.2.x.
For Duplex deployment, all the steps must be performed on both active and standby server. You must first start the upgrade process with the standby server.

Performing the pre-upgrade steps

Sl. no.
Task
Reference
1
Take a snapshot of the existing Communication Manager virtual machine.
2
Take a full backup of the existing Communication Manager
For more information about creating a backup, see Creating a full backup.
3
Identify the host on which Communication Manager is running. Identify whether the ESXi host is a vCenter managed or a standalone host.
Identify the host to which Communication Manager will be upgraded. Identify whether the ESXi host is a vCenter managed or a standalone host.
Go to ServicesSolution Deployment ManagerApplication Management.
Under the Application Management Tree, you can see if the ESXi host is a vCenter managed or a standalone host.
4
When using System Manager Solution Deployment Manager, ensure that sufficient memory and space is available for the server that you have attached with the software library.
Login to SMGR CLI as a root user, and enter the following:cd /
df
List of available directories and the disk space usage details appear. Ensure that the /swlibrary directory has enough space.
5
Create a user in vCenter with administrator credentials to gain access for the applications using HTTP, FTP, SCP or SFTP services.
-
6
For the existing Communication Manager application instance, ensure that the user credentials specified while adding Communication Manager instance in System Manager can login to the Communication Manager SMI.
Additionally, ensure that the same admin user must belong to the Profile 18 (prof18) user profile group.
For more information on creating an administrator user, see Creating a Privileged Administrator login.
For more information on viewing the profile 18 user, see Viewing the admin account for profile 18.
7
Configure SNMP access for the Communication Manager user.
You must configure SNMP access for:
  • SNMP Version 1 for read-only
  • SNMP Version 1 for write-only
For the Communication Manager application instance, make sure that the Read Community and Write Community used in the System Manager's InventoryManage ElementsSelect CMEditSNMP attributes tab, is same in Communication Manager SMI.
For more information on configuring SNMP access, see Configuring SNMP access for the Communication Manager user.
For more information about the SNMP configuration details on the Communication Manager SMI, see Viewing the SNMP configuration.
8
Add the Communication Manager application license file.
For more information about licensing, see License file for Communication Manager.
9
Configure user settings
For more information about user settings, see User settings
10
Ensure that you have the PLDS access credentials and Company ID.