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

Upgrading to Prime Central for HCS 9.1.1

Table Of Contents

Upgrading to Prime Central for HCS 9.1.1

Upgrading Prime Central for HCS with Zero Downtime

Upgrading Prime Central for HCS Inline

Before Upgrading Prime Central for HCS

Cloning the VM

Performing SAN Alignment

Upgrading to Prime Central for HCS 9.1.1

With Remotely Staged Files

With Locally Staged Files on the Target Installation Box

Recovering from a Failed Upgrade Procedure


Upgrading to Prime Central for HCS 9.1.1


This chapter explains the procedure to upgrade your Prime Central for HCS 1.0.1 or from Prime Central for HCS 1.1 to Prime Central for HCS 9.1.1. If you had previously installed Prime Central for HCS 1.0.1 or Prime Central for HCS 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 or 1.1 to Prime Central for HCS 9.1.1, you can perform any of the following upgrades:

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

Zero 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.


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 uninstalled the components from the VM due to any reason, you must perform a fresh installation. In that case, do not run the upgrade scripts. This chapter contains the following sections:

Upgrading Prime Central for HCS with Zero Downtime

Upgrading Prime Central for HCS Inline

Recovering from a Failed Upgrade Procedure

Upgrading Prime Central for HCS with Zero Downtime

A typical upgrade procedure spans approximately 2 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 Prime Central for HCS Inline.

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

1. Create a New VLAN

2. Upload the Prime Central for HCS Media

3. Clone the VMs

4. Verify Clones

5. Upgrade VM Hardware

6. Deactivate DMA-IM on HCM-F Clone

7. Perform Prime Central for HCS Upgrade

8. Verify Upgrade

9. Switch VLAN

10. Reprovision Devices on IM

11. Post-Upgrade Cleanup

Create 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.

Step 9 Verify that the LUN has enough space for the clones.


Upload 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.

Clone 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 which need to be cloned are:

Prime Central for HCS VMs—all 5 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.

The following steps have to be performed once for each component that has to be cloned. This can be done in parallel.


Step 1 After the 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 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.


Verify Clones

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

The clones power on successfully.

The expected processes on the 5 components run as expected. For more information, see Running Process.

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

If any of the above is not met, perform the procedure to clone the VMs again.

Upgrade VM Hardware

If necessary, you must upgrade the VM hardware from version 7 to version 8 before attempting to upgrade 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 in to 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.


Deactivate DMA-IM on HCM-F Clone

You must deactivate the DMA-IM on the HCM-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

Perform Prime Central for HCS Upgrade

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 Prime Central for HCS Inline.


Verify 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 5 components run as expected. For more information, see Running Process

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

Switch VLAN

After the upgrade procedure completes, you have switch the VLANs of the 5 components of Prime Central for HCS. You must not switch 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.


Reprovision Devices on IM

On HCL-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

Post-Upgrade Cleanup

This step 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.

If you plan on moving the original VMs back to the production VLAN, you must then revert to the original MAC address (which was recorded during the clone process). If the original MAC address is not restored, the applications may not work as designed.

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 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. 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 Prime Central for HCS Inline

You can upgrade your Prime Central for HCS using one of the following two methods. Before you attempt to upgrade, you must perform some preliminary tasks. This section contains the following topics:

Before Upgrading Prime Central for HCS

Upgrading to Prime Central for HCS 9.1.1


Note Before you attempt to upgrade your working system to version 9.1.1, we recommend that you create a clone of the Prime Central for HCS 1.0.1 or Prime Central for HCS 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 you attempt to upgrade 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.1.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, against 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 screenshots that were captured during the various stages of this procedure. We strongly recommend that you periodically verify if the path depicted on the screenshots matches that of your system.


This procedure must be repeated for each VM. All operations below 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.1.1, you have the option of performing SAN alignment manually or performing a fresh installation using OVA files.

However, you must be aware that if you choose to perform SAN alignment, it is safe to account for additional time required for the procedure to complete. The upgrade procedure, excluding SAN alignment, can take 2 hours or more. The upgrade time varies based on the number of domain managers Infrastructure Monitoring monitors; the more the number of domain managers, the longer it takes to complete the upgrade procedure.


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 not, a volume group configuration, which is not a default one, is in use. Contact Cisco Support for further assistance. See Figure 5-2.

Figure 5-2

Output for Command vgdisplay—Example

b. Run the command lvdisplay.

LV Name—There must be two logical volumes. If not, logical volume set up, which is not a default one, is in use. Contact Cisco Support for further assistance. See Figure 5-3.

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 From the output, verify the 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)

If either of the above is missing or is different, mount point values, which are not the default values, are in use. Contact Cisco Support for further assistance.

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 Against Virtual Device Node, select SCSI (0:1).


Tip For better performance, we recommend that you choose Eager Zero instead of Lazy Zero.


Step 7 Run the command shutdown -r now.

Step 8 Reboot the VM.

Step 9 Log in as root user.

Step 10 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 11 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 12 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 13 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 14 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 15 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 16 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 17 At the Command (m for help) prompt, run the command p to verify if the Start value of /dev/sda2 is 208845.

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

Step 19 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 20 Run the command n.This creates a new partition.

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

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

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

Step 23 Choose the start sector.

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

Figure 5-14

Output for Command n—Example

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

Step 26 Enter the partition number as 2.

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

Figure 5-15

Output for Command t—Example

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

Figure 5-16

Output for Command w—Example

Step 29 Run the command shutdown -r now.

Step 30 Reboot the VM.

Step 31 Log in as root user.

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

Step 33 Create a physical volume dev/sdb. Run the command pvcreate /dev/sda2.

Step 34 Extend the volume group. Run the command vgextend VolGroup00 /dev/sda2.

Step 35 Move the physical volumes. 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 36 Remove the physical volume /dev/sda2 from VolGroup00. Run the command vgreduce VolGroup00 /dev/sdb.

Step 37 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 38 Run the command shutdown -h now to shut down the VM.

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

Step 40 Restart the VM.

SAN alignment is now complete.


Upgrading to Prime Central for HCS 9.1.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 using either `Remotely Staged Files' method or `Locally Staged Files on the Target Installation Box' method.

With Remotely Staged Files

With Locally Staged Files on the Target Installation Box


Note Run the upgrade steps in the order mentioned below.



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


You can begin the upgrade procedure of the various components. The following three rules apply:

Log in as root user

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

With Remotely Staged Files

Prime Central Upgrade

Follow the procedure given below to upgrade Prime Central component.


Step 1 Log in 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 ]


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

The length of the hostname must not exceed 18 characters.

The prime_upgrade_push.py directory must be the same directory that you used while installing Prime Central for HCS 1.0.1 or Prime Central for HCS 1.1.

We recommend that you maintain the same VM root password across all the VMs.

Prime hostname—In the above command, provide only the hostname against <prime-hostname> argument. hostname must contain only lowercase characters. Do not enter the IP address.

Admin Password—In the above command, against the argument--admin-password, provide the password that you entered at the time of installation of version 1.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 (-) and percentage (%) must not be used.

Prime Admin Password—Against the argument <prime_admin_password>, provide a complicated 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. The -<prime_admin_password> can be the same as that of <orig_prime_admin_password>; if you specified the same password as that or <orig_prime_admin_password>, the password will not change during the upgrade process. Else, the password will change to the newer password. 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 Prime Central Upgrade—Example.

Event Collector Upgrade

Upgrade the Event Collector component following the procedure below:


Step 1 Log in 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> ]
[ --ssh-host <ssh-host-or-ip> --ssh-port <ssh-port> ] [ --ssh-push-key ]


Follow the guidelines below before you supply variables:

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

The length of the hostname must not exceed 18 characters.

You will prompted to enter the Prime Central VM root password unless you set the SSH to not prompt for a password from Event Collector VM to Prime Central VM for root user. We recommend that you maintain the same VM root password across all the VMs.

Prime hostname—In the above command, provide only the hostname against <prime-hostname> argument. Hostname must contain only lowercase characters. Do not enter the IP address.

Admin Password—In the above command, against the argument--admin-password, 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 (-) and percentage (%) must not be used.

Prime Admin Password—Against the argument --prime-admin-password, provide a complicated 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. The --orig-prime-admin-password is the --prime-admin-password that you used at the time of installing version 1.0.1 or 1.1. If you are upgrading from Prime Central for HCS 1.0.1, you must provide the same password for the --orig-prime-admin-password and --prime-admin-password argument. 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 Event Collector Upgrade—Example.

Correlation Engine Upgrade

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


Step 1 Log in 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 ]


Follow the guidelines below before you supply variables:

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

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 Correlation Engine.

The length of the hostname must not exceed 18 characters.

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.

In the above command, against the argument --admin-password, provide a complicated password for users in the Prime Central VM. The password must be the same in all the five VMs. If different passwords are used, you run the risk of having to reinstall the components. The -<prime_admin_password>can be the same as that of <orig_prime_admin_password>; if you specified the same password as that or <orig_prime_admin_password>, the password will not change during the upgrade process. Else, the password will change to the newer password. 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 (-) and percentage (%) must not be used.

To see an example of the usage of the script, see Correlation Engine Upgrade—Example.

Service Visualizer Upgrade

Service Visualizer upgrade requires 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 installer. Before you begin the upgrade procedure, ensure that the Prime Central VM restarted after the reboot.

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


Step 1 Log in 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-hostname-DO-NOT-USE-IP> --ec-hostname <event-collector-host-or-ip> --prime-hostname <prime-hostname-DO-NOT-USE-IP>

--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> ]
[ --ssh-host <ssh-host-or-ip> --ssh-port <ssh-port> ] [ --ssh-push-key ]


Make note of the following guidelines while supplying variables:

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

The length of the hostname must not exceed 18 characters.

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 Service Visualizer.

You will prompted to enter the Prime Central VM root password unless you set the SSH to not prompt for a password from Event Collector VM to Prime Central VM for root user. We recommend that you maintain the same VM root password across all the VMs.

Prime hostname—In the above command, provide only the hostname against <prime-hostname> argument. Hostname must contain only lowercase characters. Do not enter the IP address. The value that you enter against the --prime-hostname argument must be the same hostname that you entered during installation of Prime Central.

Admin Password—In the above command, against the argument--admin-password, 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 (-) and percentage (%) must not be used.

Prime Admin Password—Against the argument --prime-admin-password, provide a complicated 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. The -<prime_admin_password> can be the same as that of <orig_prime_admin_password>; if you specified the same password as that or <orig_prime_admin_password>, the password will not change during the upgrade process. Else, the password will change to the newer password. 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 Service Visualizer Upgrade—Example.

Infrastructure Monitoring Upgrade

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


Step 1 Log in 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 ]


Make note of the following guidelines while supplying variables:

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

The length of Infrastructure Monitoring hostname must not exceed 18 characters.

You will prompted to enter the Prime Central VM root password unless you set the SSH to not prompt for a password from Infrastructure Monitoring VM to Prime Central VM for root user. We recommend that you maintain the same VM root password across all the VMs.

In the above command, against the argument --admin-password, provide a complicated password for users in the Prime Central VM. The password must be the same in all the five VMs. If different passwords are used, you run the risk of having to reinstall the components. The -<prime_admin_password>can be the same as that of <orig_prime_admin_password>; if you specified the same password as that or <orig_prime_admin_password>, the password will not change during the upgrade process. Else, the password will change to the newer password. If you do not specify the passwords in the command line argument, you will be prompted to supply one at the time of installation. The password must follow the guidelines mentioned below:

Minimum 5 characters and maximum 14 characters.

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

To see an example of the usage of the script, see Infrastructure Monitoring Upgrade—Example.

With Locally Staged Files on the Target Installation Box

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.

Prime Central Upgrade


Step 1 Log in 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>


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

The length of the hostname must not exceed 18 characters.

The prime_upgrade.py directory must be the same directory that you used while installing Prime Central for HCS 1.0.1 or Prime Central for HCS 1.1.

Prime hostname—In the above command, provide only the hostname against <prime-hostname> argument. Hostname must contain only lowercase characters. Do not enter the IP address.

Admin Password—In the above command, against the argument--admin-password, 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 (-) and percentage (%) must not be used.

Prime Admin Password—Against the argument --prime-admin-password, provide a complicated 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. The -<prime_admin_password> can be the same as that of <orig_prime_admin_password>; if you specified the same password as that or <orig_prime_admin_password>, the password will not change during the upgrade process. Else, the password will change to the newer password. 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 Prime Central Upgrade—Example.

Event Collector Upgrade


Step 1 Log in 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> ]

 
   

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

The length of the hostname must not exceed 18 characters.

You will prompted to enter the Prime Central VM root password unless you set the SSH to not prompt for a password from Event Collector VM to Prime Central VM for root user.

Prime hostname—In the above command, provide only the hostname against <prime-hostname> argument. Hostname must contain only lowercase characters. Do not enter the IP address.

Admin Password—In the above command, against the argument--admin-password, 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 (-) and percentage (%) must not be used.

Prime Admin Password—Against the argument --prime-admin-password, provide a complicated 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.The --orig-prime-admin-password is the --prime-admin-password that you used at the time of installing version 1.0.1 or 1.1. If you are upgrading from Prime Central for HCS 1.0.1, you must provide the same password for the --orig-prime-admin-password and --prime-admin-password argument if upgrading from 1.0.1 to 9.1.1 release. 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 Event Collector Upgrade—Example.

Correlation Engine Upgrade

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); 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. Additionally, you must clear all source control file locks since locks persist through the session despite logging out of the Correlation Engine GUI.

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


Step 1 Log in 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 guidelines while supplying values for the variables:

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

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 Correlation Engine.

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.

In the above command, against the argument --admin-password, provide a complicated password for users in the Prime Central VM. The password 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 5 characters and maximum 14 characters.

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

To see an example of the usage of the script, see Correlation Engine Upgrade—Example.

Service Visualizer Upgrade

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 installer. You must begin installing the Service Visualizer component only after Prime Central VM is up and running after the reboot.

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


Step 1 Log in 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> ]


Make note of the following guidelines while supplying variables:

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

The length of the hostname must not exceed 18 characters.

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 Correlation Engine.

You will prompted to enter the Prime Central VM root password unless you set the SSH to not prompt for a password from Event Collector VM to Prime Central VM for root user.

Prime hostname—In the above command, provide only the hostname against <prime-hostname> argument. Hostname must contain only lowercase characters. Do not enter the IP address. The value that you enter against the --prime-hostname argument must be the same hostname that you entered during installation of Prime Central.

Admin Password—In the above command, against the argument--admin-password, 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 when you upgrade. The password must follow the guidelines mentioned below:

Minimum 5 characters and maximum 14 characters

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

Prime Admin Password—Against the argument --prime-admin-password, provide a complicated 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. The -<prime_admin_password>can be the same as that of <orig_prime_admin_password>; if you specified the same password as that or <orig_prime_admin_password>, the password will not change during the upgrade process. Else, the password will change to the newer password. If you do not specify the passwords in the command line argument, you will be prompted to supply 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 Service Visualizer Upgrade—Example.

Infrastructure Monitoring Upgrade

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


Step 1 Log in 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> ]


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

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

The length of Infrastructure Monitoring hostname must not exceed 18 characters.

In the above command, against the argument --admin-password, provide a complicated password for users in the Prime Central VM. The password 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 at the time of installation. The password must follow the guidelines mentioned below:

Minimum 5 characters and maximum 14 characters.

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

To see an example of the usage of the script, see Infrastructure Monitoring Upgrade—Example.

Recovering from a Failed Upgrade Procedure

Before you attempt to upgrade your working system to version 9.1.1, we recommend that you create a clone of the Prime Central for HCS 1.0.1 or 1.1 VMs with vCenter; this will help you rollback to version 1.0.1 or 1.1, in case the upgrade procedure fails due to some reason. This has to be done when the VMs are powered off.

However, if you do not have clones of the virtual machines, you must uninstall all 5 components of Prime Central for HCS and perform a fresh installation.