Cisco Prime Central for Hosted Collaboration Solution 9.2.1 Installation Guide
Chapter 5: Upgrading to Prime Central for HCS 9.2.1
Downloads: This chapterpdf (PDF - 734.0KB) The complete bookPDF (PDF - 2.19MB) | Feedback

Upgrading to Prime Central for HCS 9.2.1

Table Of Contents

Upgrading to Prime Central for HCS 9.2.1

Upgrading to Prime Central for HCS with Minimal Downtime

Upgrading to Prime Central for HCS Inline

Before Upgrading Prime Central for HCS

Cloning the VM

Performing SAN Alignment

Upgrading to Prime Central for HCS 9.2.1

Upgrading With Remotely Staged Files

Upgrading With Locally Staged Files on Target Machine

Recovering from a Failed Upgrade Procedure


Upgrading to Prime Central for HCS 9.2.1


This chapter explains the procedure to upgrade your Prime Central for HCS 1.0.1, 1.1 or 9.1.1 to 9.2.1. If you had previously installed Prime Central for HCS 1.0.1, 1.1, or 9.1.1 in your environment, you can either perform a fresh installation or perform an upgrade.

To upgrade from Prime Central for HCS 1.0.1, 1.1, or 9.1.1 to 9.2.1, you can perform any of the following upgrades:

Inline Upgrade - No extra resources are needed but results in about 4 hours of intermittent downtime.

Minimal Downtime Upgrade - Requires extra resources but downtime is only for few seconds.


Note After you complete the upgrade procedure of each component, the virtual machine reboots. This is to turn on the SELinux feature. The virtual machine does not reboot if SELinux enforcing mode is permissive before upgrade. Verify that the LUN has enough space for the clones. The upgrade time is directly proportional to the number of domain managers monitored by the Infrastructure Monitoring component server. The greater the number of domain managers monitored the longer the upgrade process takes.


Before you upgrade, you must perform SAN alignment. This procedure must be done for each of the VMs. For more information, see Performing SAN Alignment.

If you uninstall the components from the VM, you must perform a fresh installation. In that case, do not run the upgrade scripts. This chapter contains the following sections:

Upgrading to Prime Central for HCS with Minimal Downtime

Upgrading to Prime Central for HCS Inline

Recovering from a Failed Upgrade Procedure

Upgrading to Prime Central for HCS with Minimal Downtime

A typical upgrade procedure spans approximately 4 hours. The inline upgrade procedure results in about 2 hours of intermittent downtime, but does not require extensive lab setup and extra resources. We recommend that you follow the inline upgrade procedure available at Upgrading to Prime Central for HCS Inline.

However, if you wish to bypass the inline upgrade procedure, you can follow the upgrade procedure with minimum downtime. Follow the procedure in the order specified below to upgrade your Prime Central for HCS software with minimum downtime:

1. Creating a New VLAN

2. Uploading the Prime Central for HCS Media

3. Cloning the VMs

4. Verifying Clones

5. Upgrading VM Hardware

6. Deactivating DMA-IM on an HCM-F Clone

7. Upgrading to Prime Central for HCS

8. Verifying the Upgrade

9. Switching the VLAN

10. Reprovisioning Devices on IM

11. Performing Post-Upgrade Cleanup

Creating a New VLAN


Step 1 Log in to vSphere for the vCenter that contains the Prime Central component and HCM-Fulfillment VM.

Step 2 Select the desired host, and click Configuration tab.

Step 3 From the left pane, from the Hardware pane, select Networking.

The Networking page appears.

Step 4 From the top right corner of the page, select Add Networking....

The Add Network Wizard page.

Step 5 From the Connection Types area, click Virtual Machines.

The Network Access page appears.

Step 6 Select the Create a vSphere Standard Switch radio button.


Note No VNIC must be selected.


The Connection Settings page appears.

Step 7 Against the Port Group Properties, enter the following details:

Network Label—A descriptive network name

VLAN ID—The default value of None(0).

The Summary page appears.

Step 8 Click Finish.


Uploading the Prime Central for HCS Media

Upload the media to a Linux VM. The VM should be made available in the isolated network. To reduce the resources, we recommend that you upload the media to the Prime Central VM. Also, if you upload the media before the VM is cloned, the media will be accessible in the new VLAN. The recommended location to store the media is /opt.

Cloning the VMs

Before you proceed to upgrade, you must clone the VMs in an isolated network. By doing this, the original VMs can continue monitoring the solution while the clones are being upgraded. When you clone in an isolated network and upgrade your Prime Central for HCS software, the following sequence of events occurs:

1. The isolated network allows the Prime Central for HCS VMs to retain the same hostname, IP, and MAC address as required by the components.

2. Once the upgrade is complete, the original and upgraded VMs can be swapped by changing the VLANs.

3. Now, the upgraded clones are on the active network and the originals are isolated. The downtime will, at this point (switching VLANs), be around 5 minutes. The data loss is limited to the 5-minute downtime. The final cloned, upgraded instance will have no knowledge of events occurring after the cloning of the original VMs begin. After the switchover is performed, you can use the original VMs, now in the isolated network, to view events which occurred between the clone and switchover processes.

The VMs that needs to be cloned are:

Prime Central for HCS VMs—all five components

DNS

NTP

HCM-Fulfillment

If NTP and/or DNS are not VMs or you prefer to not clone the VMs, the administrator must create a temporary VM to represent the NTP/DNS server on the isolated network. This temporary VM be identified with the same IP and hostname as the actual NTP/DNS server in production.


Note When you clone all the 8 VMs parallely, it may consume sufficient IOPS on the SAN to potentially impact overall system performance. This is especially true if the VMs all are being cloned from the same source LUN and being placed on the same target LUN. The source LUN and Target LUN can potentially be the same LUN, which increases the potential IOPS issue.


The following steps have to be performed once for each component that has to be cloned and this can be done in parallel:


Step 1 After the Prime Central for HCS VM is configured, right-click the VM in vSphere, and click Clone.

The Name and Location window appears.

Step 2 Provide a name for the VM clone and select a datacenter. Ensure that you select the appropriate datacenter. Click Next.

The Host / Cluster window appears.

Step 3 Select the appropriate cluster. Click Next.

The Specify a Specific Host window appears.

Step 4 Select a hostname for the clone. Click Next.

The Storage window appears.

Step 5 Select the appropriate storage location. Click Next.

The Guest Customization window appears.

Step 6 Choose the Do not customize radio button. Click Next.

The Ready to Complete window appears.

Step 7 Click Finish.

Step 8 Right-click the virtual machine, and choose Edit Virtual Machine Settings button.

The Virtual Machine Properties window appears.

Step 9 From the Hardware pane, choose Network Adapter. From the details that appear, change the following values:

MAC address area—In the MAC address field, override the VM MAC address to match the original. This field is enabled only after you select the Manual radio button.


Note Keep a record of the original MAC address of the VM.


Network Connection area—From the Network Label drop-down list, select the new isolated VLAN.

Click OK.

Step 10 After the procedure is complete, power up the cloned VMs (located in the upgrade VLAN) in the following order:

1. DNS

2. NTP

3. HCM-Fulfillment

4. Prime Central

5. Event Collector

6. Correlation Engine

7. Service Visualizer

8. Infrastructure Monitoring

Step 11 Optional Step—If you want to upgrade the VM hardware, see Upgrading VM Hardware.

Step 12 Optional Step—If you require to access the Prime Central for HCS GUI in the isolated VLAN, you can clone a VM with Windows and then move it to the isolated VLAN. You can skip this step if you require to access only console sessions for each component.


Verifying Clones

You need to verify the clones before you attempt to upgrade your software. Ensure the following criteria are met:

The clones power on successfully.

The expected processes on the five components run as expected. For more information, see Processes and Log Files.

Prime Central for HCS GUI is accessible (if you cloned a Windows VM).

If any of the criteria are not met, perform the cloning procedure again.

Upgrading VM Hardware

You must upgrade the VM hardware from version 7 to version 8 before upgrading the PC4HCS applications. Only the PC4HCS VM hardware should be upgraded during this window.

You can upgrade virtual hardware on multiple virtual machines in a single operation by using the Virtual Machines tab. To upgrade virtual hardware on multiple virtual machines:


Step 1 Start the vSphere Client or vSphere Web Client, and log into the vCenter Server.

Step 2 Select Inventory > Hosts and Clusters.

Step 3 Select the host or cluster that contains the VMs to upgrade.

Step 4 Click the Virtual Machines tab.

Step 5 Select and power off the virtual machines to upgrade.

Step 6 Right-click your selections. Select Upgrade Virtual Hardware and click Yes.

Step 7 Power on the virtual machines.


Deactivating DMA-IM on an HCM-F Clone

You must deactivate the DMA-IM on the HCS-Fulfillment clone VM, which is present in the new isolated VLAN. On the HCM-Fulfillment clone VM, from the admin CLI, run the following commands:

admin:utils service stop Cisco HCS DMA-IM Service

admin:utils service deactivate Cisco HCS DMA-IM Service

Upgrading to Prime Central for HCS

To access the Prime Central for HCS media, open a console session to the VM which contains the media in the upgrade network.


Step 1 To open a console session, right-click, and choose Open Console.

Step 2 Log in with the appropriate user credentials to the console session.

Step 3 In the console session, open a terminal. To open a terminal, from the menu bar, click Applications > Accessories > Terminal. Navigate to the location which contains the media.

Step 4 Perform the normal upgrade procedure. For more information, see Upgrading to Prime Central for HCS Inline.


Verifying the Upgrade

To verify if the upgrade process was success, perform the following checks:

Verify if the upgrade logs indicate that the upgrade process was successful

Verify if the expected processes on the five components run as expected. For more information, see Processes and Log Files.

Prime Central for HCS GUI is accessible (if you cloned a Windows VM).

Switching the VLAN

After the upgrade procedure completes, you have to switch the VLANs of the five components of Prime Central for HCS. You must not switch the VLANs of DNS, NTP, or HCM-Fulfillment servers. Switch the VLANs in the following order:

1. Prime Central

2. Event Collector

3. Correlation Engine

4. Service Visualizer

5. Infrastructure Monitoring

You have to perform this procedure once for each component:


Step 1 Right-click the production VM in vSphere, and choose Edit Virtual Machine Settings button.

The Virtual Machine Properties window appears.

Step 2 From the Hardware pane, choose Network Adapter. In the Network Connection area, from the Network Label drop-down list, select the new upgrade VLAN.

Click OK.

Step 3 Right-click the upgrade VM in vSphere, and choose Edit Virtual Machine Settings button.

The Virtual Machine Properties window appears.

Step 4 From the Hardware pane, choose Network Adapter. In the Network Connection area, from the Network Label drop-down list, select the production VLAN.

Click OK.


Reprovisioning Devices on IM

On HCM-Fulfillment production server, from the Admin CLI, execute the reprovision command. This allows the DMA-IM to start provisioning any new devices to be monitored by IM:

admin:utils reprovision im_monitored_devices

Performing Post-Upgrade Cleanup

This procedure is optional. This procedure helps you cleanup space and name components appropriately. If required, you can use the original Prime Central for HCS VMs, which are now in the isolated VLAN, as a backup.

You can remove the Prime Central for HCS, HCM-Fulfillment, DNS, and NTP VMs from the isolated network once you have determined that the historical data is no longer needed. To do this:


Step 1 Power down the VM.

Step 2 Right-click the VM and selecting Delete from Disk.


Before you delete the old VMs, be sure to run a backup on the upgraded production system. A previous backup on the old version cannot be used on the new version. To free disk space, we recommend that you remove Prime Central for HCS media from the Prime Central component.

Additionally, you can provide a more-relevant name for the VMs on vCenter. This is effective only for the name in the vCenter's database and not on the DNS name used by the HCS. From vSphere, perform the following steps:


Step 1 Go to Home > Hosts and Clusters.

Step 2 Right click the VM and select Rename.

Step 3 Enter an appropriate name.


Upgrading to Prime Central for HCS Inline

Before you attempt to upgrade, you must perform some preliminary tasks and then perform the upgrade. This section lists the relevant tasks to be performed before and also during the upgrade process:

Before Upgrading Prime Central for HCS

Upgrading to Prime Central for HCS 9.2.1


Note Before you attempt to upgrade your working system to version 9.2.1, we recommend that you create a clone of the Prime Central for HCS 1.0.1, 1.1, or 9.1.1 VMs with vCenter; this will help you rollback to the previous version, in case the upgrade procedure fails due to some reason. It is critical that you power down the VMs before you attempt to capture a clone. For the cloning procedure, see Cloning the VM.


Before Upgrading Prime Central for HCS

This section explains the steps that you must perform before upgrading your Prime Central for HCS software. The following steps are involved:

1. Cloning the VM

2. Performing SAN Alignment

Cloning the VM

The following procedure explains the steps involved in cloning your VM. We recommend that you create a clone of your VM before you attempt to upgrade to Prime Central for HCS 9.2.1.


Step 1 After the Prime Central for HCS VM is configured, right-click the VM in vSphere, and click Clone.

The Name and Location window appears.

Step 2 Provide a name for the VM clone and select a datacenter. Ensure that you select the appropriate datacenter. Click Next.

The Host / Cluster window appears.

Step 3 Select the appropriate cluster. Click Next.

The Specify a Specific Host window appears.

Step 4 Select a hostname for the clone. Click Next.

The Storage window appears.

Step 5 Select the appropriate storage location. Click Next.

The Guest Customizing window appears.

Step 6 Choose the Do not customize radio button. Click Next.

The Ready to Complete window appears.

Step 7 Click Finish.

Step 8 Power down the VM.

Step 9 Right-click the virtual machine, and choose Edit Virtual Machine Settings button.

The Virtual Machine Properties window appears.

Step 10 From the Hardware pane, choose Network Adapter. From the details that appear, for the MAC address field, override the VM MAC address to match the original. This field is enabled only after you select the Manual radio button.


Note Keep a record of the original MAC address of the VM.



Performing SAN Alignment

The following procedure helps you perform SAN alignment before an upgrade procedure. You need to perform the SAN alignment procedure only once. If you had performed this earlier, you can skip this step.


Note This section contains screen shots that were captured during the various stages of this procedure. We strongly recommend that you periodically verify if the path depicted on the screen shots matches that of your system.


This procedure must be repeated for each VM. All operations must be done using the VMWare console and not over a remote session such as an SSH session.

Manual SAN alignment does not include boot partition. If you are upgrading from Prime Central for HCS 1.0.1 to Prime Central for HCS 9.2.1, you have the option of performing SAN alignment manually or performing a fresh installation using OVA files.

If you are planning to perform SAN alignment for your VMS, you must increase the maintenance window to allow additional time required to complete the SAN alignment. This time is over and above the normal upgrade procedure time. The upgrade procedure, excluding SAN alignment, can take 4 hours or more.


Step 1 Clone the VM being upgraded. This is to ensure the availability of a backup in case the SAN alignment fails.

Step 2 Verify that there is a single hard disk and the hard disk partitioning has default partition layout. If the partitioning is different from the default partition layout, contact Cisco support. See Figure 5-1.

Figure 5-1

Default Partition Layout—Example


Note The disk size of a virtual machine will change based on the component.


a. Verify that there are only two partitions: /dev/sda1 and /dev/sda2.

b. Verify that the Start value for /dev/sda2 is 208845.

Step 3 Verify the following disk configurations:

a. Run the command vgdisplay.

VG Name—There must be a single volume group VolGroup00. If you do not have the configuration shown in Figure 5-2, you are using a non-standard, non-default volume group configuration.

Figure 5-2

Output for Command vgdisplay—Example

b. Run the command lvdisplay.

LV Name—If you do not have two logical volume names as shown in Figure 5-3, you are using a non-standard and non-default configuration.

Figure 5-3

Output for Command lvdisplay—Example

c. Run the command mount. See Figure 5-4.

Figure 5-4

Output for Command mount—Example

Step 4 In the output, verify if the following values appear:

Output of / must be /dev/mapper/VolGroup00-LogVol100 on / type ext3 (rw)

(As depicted alongside first arrow)

Output of /boot must be /dev/sda1

(As depicted alongside second arrow)

Either the boot details are not found or different mount points are only shown if you are using a non-standard and non-efault configurations.

Step 5 Add a new hard disk to the VM. Follow the specifications listed below:

Size—The size must be the same as that of the existing (first) hard disk.

Disk Format—Thick disk format.

Click Next.

Step 6 Right-click the VM that is going to get the new hard disk and select Edit Settings.

Step 7 Click Add.

Step 8 Select Hard Disk from the list of available devices and click Next.

Step 9 From the Disk tab, select Create a new virtual disk.

Step 10 Click Next.

Step 11 In the Capacity tab, set the new disk size (must match the exiting hard disk size).

Step 12 In the Disk Provisioning tab, select Thick Provision Eager Zero.

Step 13 In the Location tab, select Store with the virtual machine and click Next.

Step 14 From the Virtual Device Node section, select SCSI (0:1) from the drop-down list and click Next.

Step 15 Review the information in the Options tab and click Finish.

Step 16 Click Back if you want to make changes to the selections.

Step 17 Run the command shutdown -r now.

Step 18 Reboot the VM.

Step 19 Log into the staging media VM as root user.

Step 20 Run the command init 1

To switch to single user mode wait until you see the shell prompt. See Figure 5-5.

Figure 5-5

Output for Command init1—Example

Step 21 Create a physical volume dev/sdb. Run the command pvcreate /dev/sdb. See Figure 5-6.

Figure 5-6

Output for Command pvcreate /dev/sdb—Example

Step 22 Extend the volume group. Run the command vgextend VolGroup00 /dev/sdb. See Figure 5-7.

Figure 5-7

Output for Command vgextend VolGroup00 /dev/sdb—Example

Step 23 Move the physical volumes. Run the command pvmove /dev/sda2 /dev/sdb. See Figure 5-8 and Figure 5-9.

Figure 5-8 Output for Command pvmove /dev/sda2 /dev/sdb—Example

Figure 5-9

Output for Command pvmove /dev/sda2 /dev/sdb—Example (continued)


Note This takes a few minutes to complete. Ensure that the command gets executed without errors.


Step 24 Remove the physical volume /dev/sda2 from VolGroup00. Run the command vgreduce VolGroup00 /dev/sda2. See Figure 5-10.

Figure 5-10

Output for Command vgreduce VolGroup00 /dev/sda2—Example

Step 25 Remove the labels on physical volume. Run pvremove /dev/sda2. See Figure 5-11.

Figure 5-11

Output for Command pvremove /dev/sda2—Example

Step 26 Align the partition. Run the command fdisk -u /dev/sda. See Figure 5-12.


Note -u changes the output to show sectors instead of cylinders.


Figure 5-12

Output for Command fdisk -u /dev/sda—Example

Step 27 At the Command (m for help) prompt, run the command p to verify if the Start value of /dev/sda2 is 208845.

Step 28 Run the command d. This deletes a partition.

Step 29 Enter the partition number as 2. This deletes the second partition (/dev/sda2). See Figure 5-13.

Figure 5-13

Output for Command p—Example

Step 30 Run the command n.This creates a new partition.

Step 31 Run the command p.This creates a primary partition.

Step 32 Enter the partition number as 2. The following values are listed:

First Sector (208845 - 268435455, default 208845): 208896
 
   

Step 33 Choose the start sector.

Step 34 Last sector (... default: ....): <enter>

Figure 5-14

Output for Command n—Example

Step 35 Run the command t. This changes a partition's system ID.

Step 36 Enter the partition number as 2.

Step 37 Type the Hex code as 8e. See Figure 5-15.

Figure 5-15

Output for Command t—Example

Step 38 Run the command w. This saves the partition table changes. See Figure 5-16.

Figure 5-16

Output for Command w—Example

Step 39 Run the command shutdown -r now.

Step 40 Reboot the VM.

Step 41 Log into the staging media VM as root user.

Step 42 Run the command init 1. This switches to single user mode. Wait until you see the shell prompt.

Step 43 Create a physical volume dev/sda2.

Step 44 Run the command pvcreate /dev/sda2.

Step 45 Extend the volume group.

Step 46 Run the command vgextend VolGroup00 /dev/sda2.

Step 47 Move the physical volumes.

Step 48 Run the command pvmove /dev/sdb /dev/sda2.

Ensure the command executes successfully. See Figure 5-17.

Figure 5-17

Output for Command pvmove /dev/sdb /dev/sda2—Example

Step 49 Remove the physical volume /dev/sdb from VolGroup00. Run the command vgreduce VolGroup00 /dev/sdb.

Step 50 Remove the labels on physical volume. Run pvremove /dev/sdb. See Figure 5-18.

Figure 5-18

Output for Command pvremove /dev/sdb—Example

Step 51 Run the command shutdown -h now to shut down the VM.

Step 52 Remove the second hard disk (SCSI (0:1) which maps to /dev/sdb) added to the VM earlier.

Step 53 Restart the VM.

SAN alignment is now complete.


Upgrading to Prime Central for HCS 9.2.1

After you complete the pre-upgrade steps, you are ready to upgrade your Prime Central for HCS software. The upgrade method you choose is independent of the method you used at the time of original installation—you do not have to use the method that you used at the time of installation. For example, if you used the method of Remotely Staged Files during original installation for a component, you can upgrade the same component in any of the following methods:

Upgrading With Remotely Staged Files

Upgrading With Locally Staged Files on Target Machine


Note The hostnames that you used during the installation of Prime Central for HCS 1.0.1, 1.1, or 9.1.1 must be used during the upgrade procedure.


During the upgrade process of the Prime Central for HCS component servers, the following rules apply:

Run the upgrade steps in the order mentioned in this section.

Log into the staging media VM as root user

At instances where you have to type the password, specify the root password.

Upgrading With Remotely Staged Files


Warning The restrictions for the component server password argument has changed. If your Prime Central VM root password does not meet the new restrictions, then please update the password before upgrading. If you forget to update the password, the upgrade script will show a warning message. Please exit the upgrade script and modify the password before continuing with the Prime upgrade. Only the Prime Central VM root password needs to be changed, but the other four PC4HCS components (Event Collector, Correlation Engine, Service Visualizer, and Infrastructure Monitoring) can also be changed, if desired. If the Infrastructure Monitoring password is changed then remember to update the Infrastructure Monitoring information in HCM-F or else DMA-IM will not work as designed. All upgrade CLI is executed at the remote staging server where the 9.2.1 image resides.

Upgrading Prime Central

Follow the procedure given below to upgrade Prime Central component.


Step 1 Log into the staging media VM as root user.

Step 2 Enter cd hcm_installer/scripts/hcm_install_scripts/upgrade

Step 3 Run ./prime_upgrade_push.py --prime-hostname <prime-hostname-DO-NOt-USE-IP> --ec-hostname <event-collector-host-or-ip> --hcm-f-hostname <hcm-f-hostname> --hcm-f-admin-password <hcm-f-admin-password> --im-hostname <Infrastructure-Monitoring_hostname_or_IP> --sv-hostname <service-visualizer-host-DO-NOT-USE-IP> --password <prime_vm_root_password>--ntp-servers <server1>,<server2>.... [ --admin-password <admin_password> --prime-admin-password <prime_admin_password> [ --ssh-host <ssh-host-or-ip> --ssh-port <ssh-port> ] [ --ssh-push-key ]


Guidelines for Entering Passwords and Variables

The hostnames of the components must not contain an underscore (_).

The length of the hostname must not exceed 18 characters.

Prime hostnameProvide only the hostname in the --prime-hostname argument. The hostname must contain only lowercase characters when alphabetic characters are used. Do not enter the IP address.

Admin PasswordIn the --admin-password argument, provide the password that you entered at the time of installation of version 1.0.1 or 1.1. The admin password must be the same in all the five VMs; if you specify different passwords, you run the risk of a reinstallation. If you do not specify the passwords in the command line argument, you will be prompted to supply one when you upgrade. The password must follow the guidelines mentioned below:

Minimum 5 characters and maximum 14 characters

The special characters asterisk (*), hyphen (-), percentage (%), and dollar ($) must not be used.

Use single quotes around password that has special characters such as exclamation mark (!) or ampersand (&).

Prime Admin PasswordIn the argument <prime_admin_password>, provide a strong password for users in the Prime Central VM. The prime admin passwords must be the same in all the five VMs. If different passwords are used, you run the risk of having to reinstall the components. If you do not specify the passwords in the command line argument, you will be prompted to supply one when you upgrade. The password must follow the guidelines mentioned below:

Minimum 8 characters and maximum 12 characters

A character must not be repeated 3 times consecutively.

Must contain at least one uppercase letter (A-Z).

Must contain at least one lowercase letter (a-z)

Must contain at least one number (0-9)

Must contain at least one special character @~-

The special characters exclamation mark (!), apostrophe ('), quotation mark ("), slash (/), dollar sign ($), question mark (?), accent grave (`), or underscore (_) must not be used.

Must not contain cisco or any other combination of the word.

To see an example of the usage of the script, see Upgrading Prime Central—Example.

Upgrading Event Collector

Upgrade the Event Collector component following the procedure below:


Step 1 Log into the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_scripts/upgrade

Step 3 Run ./ec_upgrade_push.py --ec-hostname <event-collector-host-or-ip> --prime-hostname <prime-hostname-or_IP> --ntp-servers <server1>,<server2>.... [ --admin-password <admin-password> --prime-admin-password <prime-admin-password> ]
[ --nco-pa-password <ec-os-root-password-from-nco_pa_crypt> ]
[
--ssh-host <ssh-host-or-ip> --ssh-port <ssh-port> ] [ --ssh-push-key ]


For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Event Collector—Example.

Upgrading Correlation Engine

The following steps explain the procedure to upgrade Correlation Engine component:


Step 1 Log into the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_scripts/upgrade

Step 3 Run ./ce_upgrade_push.py --ce-hostname <correlation-engine-host-with-domain-name-DO-NOT-USE-IP> --ec-hostname <event-collector-host-name-with-domain-name-or-ip>

--hcm-f-hostname <hcm-f-hostname> --hcm-f-admin-password <hcm-f-admin-password> --ntp-servers <server1>,<server2>....[ --admin-password <admin-password> ]
[ --ssh-host <ssh-host-or-ip> --ssh-port <ssh-port> ] [ --ssh-push-key ]


For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Correlation Engine—Example.

Upgrading Service Visualizer

Service Visualizer upgrade requires Prime Central be installed and running. Prime Central must also be reachable at the address given in the <prime-hostname-DO-NOT-USE-IP> argument for the Prime Central install script. Before you begin the upgrade procedure ensure that the Prime Central VM restarted after the reboot and is fully operational.

The following steps explain the procedure to upgrade Service Visualizer component server:


Step 1 Log into the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_scripts/upgrade

Step 3 Run ./sv_upgrade_push.py --sv-hostname <service-visualizer-host-with-domain-name-DO-NOT-USE-IP> --ec-hostname <event-collector-host-or-ip> --prime-hostname <prime-hostname-DO-NOT-USE-IP>

--hcm-f-hostname <hcm-f-host-or-ip> --hcm-f-admin-password <hcm-f-admin-password> --ntp-servers <server1>,<server2>.... [ --admin-password <admin-password> --prime-admin-password <prime-admin-password> ]
[ --ssh-host <ssh-host-or-ip> --ssh-port <ssh-port> ] [ --ssh-push-key ]


Note You will be prompted to enter a filename to save the ssh key after the image is pulled from the Staging server.




Note Use the same HCM-Fulfillment hostname and HCM-Fulfillment admin password as specified for the Prime Central upgrade. If the HCM-Fulfillment credentials have changed, then the upgrade script will update the credentials in the Service Visualizer.


For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Service Visualizer—Example.

Upgrading Infrastructure Monitoring

During the upgrade process, none of the Infrastructure Monitoring configuration (manual install steps) that you set up during the installation of Prime Central for HCS 1.0.1, 1.1, and 9.1.1 will be retained. Before you upgrade your Infrastructure Monitoring component, ensure that DMA-IM is integrated with Prime Central for HCS 9.2.1. For more information, see Integrating DMA-IM with Prime Central for HCS.


Step 1 Log into the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_scripts/upgrade

Run ./im_upgrade_push.py --im-hostname <infrastructure-monitoring-host-or-ip> --ec-hostname <event-collector-host-or-ip> --prime-hostname <prime-central-host-or-ip> --ntp-servers <server1>,<server2>....--hcm-f-hostname <HCM-F-hostname-OR-IP> --hcm-f-admin-username <HCM-F Admin CLI Username> --hcm-f-admin-password <HCM-F Admin CLI Password> [ --admin-password <admin-password> ]

[ --ssh-host <ssh-host-or-ip> --ssh-port <ssh-port>][ --ssh-push-key ]


For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Infrastructure Monitoring—Example.

Upgrading With Locally Staged Files on Target Machine

This section explains the method to upgrade the components using the Locally Staged Files method. Note the following guidelines:

Do not place the media folder under /root folder; this creates permissions issue.

Do not use /nfs mount method.

Upgrading Prime Central


Step 1 Log into the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_scripts/upgrade

Step 3 Run ./prime_upgrade.py --prime-hostname <prime-hostname-DO-NOT-USE-IP> --ec-hostname <event-collector-host-or-ip> --password <prime-vm-password> --hcm-f-hostname <hcm-f-hostname> --hcm-f-admin-password <hcm-f-admin-password> --im-hostname <infrastructure-monitoring_hostname-OR-IP> --sv-hostname <service-visualizer-host-DO-NOT-USE-IP> --password <prime_vm_root_password> --ntp-servers <server1>,<server2>....[ --admin-password <admin_password> --prime-admin-password <prime_admin_password>


For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Prime Central—Example.

Upgrading Event Collector


Step 1 Log into the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_scripts/upgrade

Step 3 Run ./ec_upgrade.py --ec-hostname <event-collector-host-or-ip> --prime-hostname <prime-hostname-OR-IP> --ntp-servers <server1>,<server2>....
[
--admin-password <admin-password> --prime-admin-password <prime-admin-password> ]
[ --nco-pa-password <ec-os-root-password-from-nco_pa_crypt> ]

 
   

For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Event Collector—Example.

Upgrading Correlation Engine

Before you begin updating the component it is important that you log out of the Correlation Engine GUI (click the Log Out button located on the top left corner). Failure to log out of the Correlation Engine GUI may cause the upgrade to fail.

non-performance of this step may result in upgrade failure. This is applicable only if you accessed the Correlation Engine GUI at any point in time before the upgrade procedure. The following steps explain the procedure to upgrade Correlation Engine component:


Step 1 Log in to the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_script/upgrade

Step 3 Run ./ce_upgrade.py --ce-hostname <correlation-engine-host-with-domain-name-DO-NOT-USE-IP> --ec-hostname <event-collector-host-name-with-domain-name-or-ip> --hcm-f-hostname <hcm-f-hostname> --hcm-f-admin-password <hcm-f-admin-password> --ntp-servers <server1>,<server2>.... [ --admin-password <admin-password> ]


Make note of the following guideline while supplying values for the variables:

In the argument <event-collector-host-name-with-domain-name-or-ip>, you can specify either the IP or hostname. If you specify the hostname, it must be used with FQDN.

For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Correlation Engine—Example.

Upgrading Service Visualizer

Service Visualizer upgrade requires that Prime Central be installed and running. Prime Central must also be reachable at the address given in the <prime-hostname> argument for the Prime Central install script. The Service Visualizer upgrade cannot being until the Prime Central component server upgrade has completed, the Prime Central VM has rebooted successfully, and the Prime Central component server is fully operational.

The following steps explain the procedure to upgrade Service Visualizer component:


Step 1 Log into the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_scripts/upgrade

Step 3 Run ./sv_upgrade.py --sv-hostname <service-visualizer-hostname-DO-NOT-USE-IP> --ec-hostname <event-collector-host-or-ip> --prime-hostname <prime-hostname>

--hcm-f-hostname <hcm-f-hostname> --hcm-f-admin-password <hcm-f-admin-password> --ntp-servers <server1>,<server2>.... [ --admin-password <admin-password> --prime-admin-password <prime-admin-password> ]


For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Service Visualizer—Example.

Upgrading Infrastructure Monitoring

During the upgrade process, none of the Infrastructure Monitoring configuration that you set up during Prime Central for HCS 1.0.1, 1.1 or 9.1.1 manual install steps will be retained. Before you upgrade your Infrastructure Monitoring component, ensure that DMA-IM is integrated with Prime Central for HCS 9.2.1. For more information, see Integrating DMA-IM with Prime Central for HCS.


Step 1 Log into the staging media VM as root user.

Step 2 Run cd hcm_installer/scripts/hcm_install_scripts/upgrade

Step 3 Run ./im_upgrade.py --im-hostname <infrastructure-monitoring-host-or-ip> --ec-hostname <event-collector-host-or-ip>--prime-hostname <prime-host-or-ip> --ntp-servers <server1>,<server2>.... --hcm-f-hostname <HCM-F-hostname-OR-IP> --hcm-f-admin-username <HCM-F Admin CLI Username> --hcm-f-admin-password <HCM-F Admin CLI Password> [ --admin-password <admin-password> ]


For password and variable related guidelines, see Guidelines for Entering Passwords and Variables. To see an example of the usage of the script, see Upgrading Infrastructure Monitoring—Example.

Recovering from a Failed Upgrade Procedure

Before attempting to upgrade a working Prime Central for HCS system to version 9.2.1, we recommend cloning each of the Prime Central for HCS 1.0.1, 1.1, or 9.1.1 VMs with vCenter. The virtual machine clones helps you to roll back to the earlier versions if the Prime Central for HCS server component's upgrade fails for any reason. This must be done when the VMs are powered off.


Note If clones of the pre-upgrade Prime Central for HCS component server virtual machines are not available, uninstall each Prime Central for HCS component server and then perform a fresh install.