This topic describes the prerequisites that you must perform before you upgrade your BMC Cloud Lifecycle Management solution in both High-Availability (HA) and non-HA environments.
The following runbook checklist provides guidelines for system requirements, upgrade sequence, and HA environment upgrade, and guidelines for the in-place upgrade option.
4.x Upgrade Checklist and Estimates.xlsx
Oracle JRE requirements
When the product installation or upgrade requires the 64-bit Oracle JRE as a prerequisite, you cannot substitute the OpenJDK version. Before you start:
- Check the Java version installed on your host.
- If the OpenJDK is installed, uninstall it and replace it with the 64-bit Oracle JRE.
- If you removed the OpenJDK and installed the Oracle JRE, verify that the environment variables are properly set to reflect the new JRE version.
Otherwise, consult the following table for which version of the Oracle JRE is required for 4.6.
Oracle JRE required for new installations or upgrades | |
|---|
| | Category 2 - Platform Manager
- Cloud Portal
- EUP
- Self Check Monitor
| |
|---|
| Oracle/Zulu 1.8 (public JRE) | - Oracle/Zulu 1.8 (public JRE)
- Use bundled JRE (1.8.0_60)
| - New installations of 4.6 require that you install two versions of the public JRE before you start the installation.
If you use the bundled JRE to install Category II products, then you need only one version of the public JRE that is required by the Category I products. - Upgrades to 4.6 require that you install two versions of the public JRE before you start the upgrade.
If you use the bundled JRE to upgrade the Category II products, then you need only one version of the public JRE that is required by Category I products.
|
Creating backups and snapshots
- Back up the Cloud Platform Manager host computer.
From the host on which you installed Cloud Platform Manager, back up the Platform_Manager folder. After you back up the Cloud Platform Manager, take a snapshot of the physical computer or VM and back up the database for Enterprise-AR and Cloud-AR at the same time.
Ensure that you can restore the database and host computers for Enterprise-AR server and Cloud-AR together. Otherwise, you might encounter possible data corruption issues. In addition, you must perform this step to save the data that the Cloud Platform Manager created on Cloud-AR.
Note
If the databases are on remote hosts, take snapshots of the remote database hosts as well.
- From the host on which you installed the preboot executable environment (PXE) server, back up the TFTP folder.
This folder is deleted on the target computer during the upgrade process. Before you upgrade the PXE server, back up your data store.
Note
Ensure that you specify the correct data store location.
- For all products that you want to upgrade in the solution:
Take a snapshot of the host on which you installed the product before you start the upgrade and when you are prompted by the installer. You can delete the extra snapshots when you finish the upgrade.
As a point of reference, during a Staged Small Deployment upgrade, approximately 45 snapshots were taken with the vCenter client:
- Back up the product database, if one exists.
For example, for BMC Atrium Core – Web Registry components, take a snapshot of the host on which you installed the web registry. For Enterprise-AR, back up the the host on which you installed the product and the database. - Review the product configuration files that are changed due to the upgrade and back them up.
Preparing for product upgrades in a non-HA environment
This section explains the steps that you must perform to prepare your product hosts for upgrading on non-HA servers.
| |
|---|
To configure the mid tier for upgrade | Configure the mid tier, so that you can use it to access Enterprise-AR and Cloud-AR: - Open the BMC Remedy Configuration Tool using the following URL:
http://<hostname>:<port>/arsys/shared/config/config.jsp
For example:
http://MidTier:8080/arsys/shared/config/config.jsp - On the AR Server Settings panel, click Add Server and specify the Enterprise-AR – Primary host name.
- On the General Settings panel, set the following fields to the Enterprise-AR – Primary host name:
- Preference Server(s)
- Data Visualization Module Server(s)
- Homepage Server
- Authentication Server
- Repeat steps 2 and 3 to add Cloud-AR to the mid tier configuration.
|
To prepare Enterprise-AR for upgrade | Before you upgrade the Enterprise-AR host, you must complete the following prerequisites: - If you are upgrading Linux, reset the symlink for /usr/java/latest to JRE installation path.
Ensure that the Enterprise-AR host has a minimum of 16 GB RAM and 4 CPUs available. Note: Ensure that you have the same amount of RAM and same number of CPUs on Cloud-AR host also. Verify that the following queue parameters are listed in the ar configuration file (ar.cfg on Windows and ar.conf on Linux): Private-RPC-Socket: 390601 1 1
Private-RPC-Socket: 390603 5 10
Private-RPC-Socket: 390620 12 12
Private-RPC-Socket: 390621 12 16
Private-RPC-Socket: 390622 4 6
Private-RPC-Socket: 390626 12 12
Private-RPC-Socket: 390635 20 20
Private-RPC-Socket: 390680 2 25
Private-RPC-Socket: 390681 4 4
Allow-Unqual-Queries: T
If the queue parameters are not present on the Enterprise-AR primary and secondary hosts, add these parameters in the ar configuration file and restart the AR System server services. If you are upgrading from 3.0 to 4.x, use BMC Remedy Developer Studio to perform the hotfix located at <Install_Planner_Dir>/Applications/AtriumCore/Common/hotfix before you upgrade BMC Atrium Core.
The following instructions are adapted from the Readme.txt. - If you are in a Linux environment, install BMC Remedy Developer Studio on a Windows host.
- Make a copy the CMU%ServiceInstances1.def file.
- On Windows, copy the file to the Enterprise-AR host.
- On Linux, copy the file to the Windows host.
- Launch BMC Remedy Developer Studio and log on to the AR System Server.
- Set Developer Studio to Base Development mode.
- Select File > Import, select the import source as Object Definitions, and then click Next.
- Browse to the CMU%ServiceInstances1.def file and then click Next.
- Select Replace Objects on the destination server and start the import
- In BMCServiceRequestManagementInstalledConfiguration.xml, set the MULTIPLE_INSTANCE_CAPABLE parameter from true to false to prevent an error message occurring during the upgrade of the Enterprise-AR SRM module (which indicates that there are multiple instances of SRM installed).
- Tune your MS SQL and Oracle databases according to the guidelines in the BMC Remedy AR System documentation: Preparing-your-database-for-an-upgrade.
Open the CMF:PluginConfiguration form for Enterprise-AR, review the following attributes, and update them if necessary.
For example: http://CLM-MT:8080/arsys/plugins/CloudCallBackPlugin/params?server=
<EnterprisePrimaryHostname>&username=csmcallback&pwd=csmcallback - Callback URI: set to the host name on which you installed the Enterprise-AR – Primary
- FIELD_AO_HOST: set to host name on which you installed BMC Atrium Orchestrator – Primary
Review the BMC.CLOUD:BMC_Callout join form on Cloud-AR host. [http://clm-mt:8080/arsys/plugins/CloudCallBackPlugin/params?server=]
<ITSMPrimartHost>&username=csmcallback&pwd=csmcallback&operation=
CHECK_CHANGE_REQUIRED - Search for the CSM Change integration HTTP Callout entry.
- Click View relationship and open the URL entry.
- From the Custom tab, review the Attribute Value with the host name on which you installed the Enterprise-AR – Primary, and update it if necessary.
- Take a snapshot of your Enterprise-AR VM and database.
- Back up any customizations that you have made to your AR System components before you upgrade or you will lose the customizations.
- If you are running an environment with two AR System servers (Enterprise-AR and Cloud-AR), use the 2AR1AR utility to merge the servers into one AR System server before you start the upgrade. For more information, see Merging-two-AR-System-servers-into-one-AR-System-server.
|
| |
To prepare BMC Server Automation Application Server for upgrade | - Update the /etc/hosts file with new hostnames of the cloned Zone 2 CLM component VMs.
- License the rscd agents of all the cloned Zone 2 CLM component VMs.
- Shut down all the BladeLogic Application Server services.
- Shut down all the BladeLogic Advanced Repeater services.
- Back up the C:\Program Files\BMC Software\BladeLogic\RSCD\daal (Windows) or /opt/bmc/bladeLogic\rscd\daal (Linux) folders.
- Take a snapshot of your Zone 1 BMC Server Automation VM.
|
To prepare BMC Server Automation PXE for upgrade | - Back up the tftp directory on the BladeLogic PXE VM.
- Shut down all the pxe and tftp services.
|
To prepare for BMC AR System Server and IT Management Suite upgrade | To ensure an efficient BMC AR System Server and IT Management Suite upgrade, see the following steps described in the BMC Remedy AR System online technical documentation: |
To prepare for a BMC AR System Server – Cloud Database upgrade | To ensure an efficient cloud database upgrade, see the following steps described in the BMC Remedy AR System online technical documentation: |
To prepare for Cloud Portal AR Extensions upgrade | Before you upgrade the Cloud Extensions, verify that DSO is working between Enterprise-AR and Cloud-AR. For example: - Log on to the Enterprise-AR System host using mid tier.
- Open the User form, search for entries in the form, and update a field on any record (for example, Email Address) for any user.
- Save the record.
- Log on to the Cloud-AR host and open the User form.
- Verify whether the user information that you modified in the previous step is now visible on the Cloud-AR host.
|
Back to top
Preparing for product upgrades in an HA environment
This section explains the steps that you must perform to prepare your product hosts for upgrading on HA servers. For recommendations for installing products in an HA environment, see Installing-products-for-HA.
| |
|---|
| |
| |
To prepare Enterprise-AR for upgrade | Before you upgrade the Enterprise-AR host, you must complete the following prerequisites: Ensure that the Enterprise-AR host has a minimum of 16 GB RAM and 4 CPUs available. Note: Ensure that you have the same amount of RAM and same number of CPUs on Cloud-AR host also. Verify that the following queue parameters are listed in the ar configuration file (ar.cfg on Windows and ar.conf on Linux): Private-RPC-Socket: 390601 1 1
Private-RPC-Socket: 390603 5 10
Private-RPC-Socket: 390620 12 12
Private-RPC-Socket: 390621 12 16
Private-RPC-Socket: 390622 4 6
Private-RPC-Socket: 390626 12 12
Private-RPC-Socket: 390635 20 20
Private-RPC-Socket: 390680 2 25
Private-RPC-Socket: 390681 4 4
Allow-Unqual-Queries: T
- If the queue parameters are not present on the Enterprise-AR primary and secondary hosts, add these parameters in ar configuration file and restart the AR System server services.
- Tune your MS SQL and Oracle databases according to the guidelines in the BMC Remedy AR System documentation: Preparing-your-database-for-an-upgrade.
- Use BMC Remedy Developer Studio to perform the hotfix located at<Install_Planner_Dir>/Applications/AtriumCore/Common/hotfix.
For detailed information on how to apply the hotfix on Windows and Linux, see Readme.txt. - Back up any customizations that you have made to your AR System components before you upgrade or you will lose the customizations.
- If you are running an environment with two AR System servers (Enterprise-AR and Cloud-AR), use the 2AR1AR utility to merge the servers into one AR System server before you start the upgrade. For more information, see Merging-two-AR-System-servers-into-one-AR-System-server.
|
To prepare DSO for upgrade in a server group | If you have installed a server group environment for the following products, ensure that you update the Distributed Server Option (DSO) for them to point to the Primary servers: - The Enterprise-AR server(all nodes in server group)--Update the DSO target with Cloud-AR – Primary host information
- Cloud-AR servers (all nodes in server group)-- Update the DSO target with the Enterprise-AR – Primary host information
- Using the mid tier, log on to any of the AR System server in the server group.
- Open the Distributed Logical Mapping form (by selecting AR System Administration Console > System > Distributed Server Option >Distributed Logical Mappings) and change the Name attribute value to the host name on which you installed the Enterprise-AR – Primary or Cloud-AR – Primary depending on the following points:
- For Enterprise-AR, specify Cloud-AR – Primary host name.
- For Cloud-AR, specify the Enterprise-AR – Primary host name.
- Using the mid tier, log on to the Primary and Secondary servers of Enterprise-AR and Cloud-AR products.
- Go to AR System Administration Console > System > General > Server Information > Connection Settings > DSO Server tab.
- Change the Server Name to the local host name on which you installed the Enterprise-AR server – Primary depending on the following points:
- For Enterprise-AR, specify Cloud-AR – Primary host name.
- For Cloud-AR, specify the Enterprise-AR – Primary host name.
- Restart the AR System Server service on the Enterprise-AR and Cloud-AR hosts.
|
To prepare the Cloud Platform Manager for upgrade | Before you upgrade the Cloud Platform Manager host, you must open the Cloudservice.JSON file and set the attributevalue parameter of Cloud-AR load balancer setting name to the host name on which you installed Cloud-AR – Primary. |
Preparing to upgrade BMC Network Automation blueprints, containers, and rogue switches
This section describes the prerequisites that you must perform before you upgrade BMC Network Automation blueprints, containers, and rogue switches.
Upgrading pod and container blueprints
The XML schema for pod and container blueprints in BMC Cloud Lifecycle Managment version 4.x contains significant differences from the previous version. Any blueprints that are in the BMC Network Automation database during the upgrade are automatically updated with the latest XML schema. Any pod and container blueprint files outside of the BMC Network Automation database will not be updated, and you will no longer be able to import those blueprint files.
If you are upgrading from BMC Cloud Lifecycle Management version 2.1 to version 4.x, BMC recommends that you perform the following procedure to upgrade your pod and container blueprints.
To upgrade pod and container blueprints:
- Locate all pod and container blueprints that you want to be able to use in your upgraded environment.
- Import all of those pod and container blueprints into BMC Cloud Lifecycle Management version 2.1.
- Upgrade BMC Cloud Lifecycle Management to version 4.x. The XML schema for all blueprint files are updated.
- Export the pod and container blueprints, if desired.
Upgrading network containers (remove multiple merge actions in a node)
Since multiple merge actions executed on the same container node to configure or unconfigure it now involve concatenation of the underlying templates involved, you should make sure that their templates do not contain unnecessary exit statements at the bottom which could interfere with this logic.