Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Prerequisites for upgrade

This section describes the prerequisites that you must perform before you upgrade your BMC Cloud Lifecycle Management solution in a High-Availability (HA) and non-HA environments. In this section, the following topics are provided:

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:

  1. Check the Java version installed on your host.
  2. If the OpenJDK is installed, uninstall it and replace it with 64-bit Oracle JRE 1.7 or later. 
  3. If you removed the OpenJDK and installed the Oracle JRE, verify that the environment variables are properly set to reflect the new JRE version. 

To create backups and snapshots

  1. Take a snapshot of the physical computer or VM and back up database for Enterprise-AR and Cloud-AR at the same time.

    Note

    If the databases are on remote hosts, take snapshots of the remote database hosts as well.  

  2. Ensure that you restore the database and host computers for Enterprise-AR server and Cloud-AR together. Otherwise, you might encounter possible data corruption issues.

    Note

    After you back up the Cloud Platform Manager host computer, ensure that you back up the hosts and databases for Enterprise-AR and Cloud-AR. You must perform this step to save the data that the Cloud Platform Manager created on Cloud-AR.

    From the host on which you installed Cloud Platform Manager, back up the Platform_Manager folder.

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

  4. Before you upgrade the PXE server, back up your data store.

    Note

    Ensure that you specify the correct data store location.

  5. For all products that you want to upgrade in the solution:

    1. Take a snapshot of the host on which you installed the product.
    2. 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.
    3. Back up the following configuration files.

    Product

    File

    Platform Manager

    Linux: <PM_Install_Directory>/Platform_Manager/wrapper.conf
    Windows: <PM_Install_Directory>\Platform_Manager/wrapper.conf

    Linux: <PM_Install_Directory>/Platform_Manager/configuration/email-templates
    Windows: <PM_Install_Directory>\Platform_Manager\configuration\email-templates

    Linux: <PM_Install_Directory>/Platform_Manager/configuration/actionCatalogs
    Windows: <PM_Install_Directory>\Platform_Manager\configuration\actionCatalogs

    Linux: <PM_Install_Directory>/Platform_Manager/configuration/cloudservice.json
    Windows: <PM_Install_Directory>\Platform_Manager\configuration\ cloudservice.json

    Linux: <PM_Install_Directory>/Platform_Manager/configuration/provider.json
    Windows: <PM_Install_Directory>\Platform_Manager\configuration\provider.json

    Enterprise-AR and Cloud-AR

    Linux:  <ARS_Home>/conf/ar.conf
    Windows: <ARS_Home>\Conf\ar.cfg

    Enterprise-AR and Cloud-AR

    Linux: /etc/arsystem/<hostname>/armonitor.conf
    Windows: <ARS_Home>\Conf\armonitor.cfg

    Enterprise-AR and Cloud-AR

    E-AR Linux:
    <ARS_Home>/pluginsvr/pluginsvr_config.xml
    <Cloud_Portal_Home>/Cloud_Portal/plugin/pluginsvr_config.xml

    E-AR Windows:
    <ARS_Home>\pluginsvr\pluginsvr_config.xml
    <Cloud_Portal_Home>\Cloud_Portal\plugin\pluginsvr_config.xml

    C-AR Linux: <ARS_Home>/pluginsvr/pluginsvr_config.xml

    C-AR Windows: <ARS_Home>\pluginsvr\pluginsvr_config.xml

    Mid Tier

    Linux: <TOMCAT_INSTALL_DIR>/conf/server.xml
    Windows    : <TOMCAT_INSTALL_DIR>\conf\server.xml

    BMC Atrium Orchestrator AMREPO

    Linux:<AMREPO_Install>/repository/config/repository.xml
    Windows: <AMREPO_Install>\repository\config\repository.xml

    BMC Atrium Orchestrator CDP

    Linux: <CDP_Install>/tomcat/webapps/baocdp/WEB-INF/classes/log4j.xml
    Windows: <CDP_Install>\tomcat\webapps\baocdp\WEB-INF\classes\log4j.xml

    BMC Network Automation

    Linux: <BCA_NETWORKS_INSTALL_DIR>/logging.properties
    Windows: <BCA_NETWORKS_INSTALL_DIR>\logging.properties 

    BMC Network Automation

    Linux: <BCA_NETWORKS_INSTALL_DIR>/tomcat/conf/server.xml
    Windows: <BCA_NETWORKS_INSTALL_DIR>\tomcat\conf\server.xml 

    BMC Network Automation

    Linux: <BCA_NETWORKS_INSTALL_DIR>/database.properties
    Windows: <BCA_NETWORKS_INSTALL_DIR>\database.properties

    BMC Database Automation

    GUI PHP Configuration (Manager Host) Linux: <BDA_Install_Dir>/etc/php.ini

    BMC Database Automation

    GUI Web Server Configuration (Manager Host)

    Linux: 

    /etc/httpd/etc/conf/httpd.conf

    /etc/httpd/etc/conf.d/gridapp.conf

Enabling logs if you run into problems

This section describes how to enable logging if you run into issues (for example, with E-AR, C-AR, Cloud Portal, or Cloud Extensions upgrades or with Cloud Portal and Cloud Extensions new installations) and you must re-run the installation or upgrade to get additional information for troubleshooting.

Note

  • These steps are optional and you should only perform them on an "as needed" basis, because they can slow down the AR System server response time during installations or upgrades.
  • The AR System must be installed before you can perform this procedure.
  1. Log on to the AR System server.
    http://<hostname:<port>/arsys 
  2. Open the AR System Administration Console (select Applications >AR System Administration >AR System Administration Console).
  3. Open the Server Information window (select System >General >Server Information).
  4. Click the Log Files tab.
  5. Enable the following logs:
    LogFiles.png
    • API Log
    • Escalation Log
    • Filter Log
    • SQL Log
    • Plug-in Log
  6. Click Apply and Save.

Preparing for an in-place upgrade

This section explains the steps that you must perform to prepare your product hosts for an in-place upgrade. 

To prepare Enterprise-AR for upgrade

Before you upgrade the Enterprise-AR host, you must complete the following prerequisites:

  1. Install Oracle JRE 1.7.

  2. Verify that the following queue parameters are listed in the ar configuration file (ar.cfg on Windows and ar.confon 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. 

To prepare Cloud-AR for upgrade

Before you upgrade the Cloud-AR host, you must complete the following prerequisites:

  1. Install Oracle JRE 1.7.
  2. If you are upgrading Linux, reset the symlink for /usr/java/latest to Oracle JRE 1.7 installation path.
  3. If you are upgrading Linux from 2.1 to 4.0, create a symlink /etc/arsystem/<stage-cloud-ar-2140>/armonitor.conf that points to /etc/arsystem/<cloud-ar>/armonitor.conf to fix an upgrade issue.
  4. Snapshot your Cloud-AR VM and database. 

To prepare BMC Server Automation for upgrade

  1. Update the /etc/hosts file with new hostnames of the cloned Zone 2 CLM component VMs.
  2. License the rscd agents of all the cloned Zone 2 CLM component VMs.
  3. Shut down the AppServer process.
  4. Snapshot your Zone 1 BMC Server Automation VM.

To prepare PXE for upgrade

  1. Back up the tftp directory on the PXE VM.
  2. Shut down the pxe and tftp processes.

To prepare BMC Network Automation 8.1 for the upgrade to 8.5

Note

These instructions apply to upgrades from 2.1.x to 4.0 if you have existing multi-zone containers or container blueprints in BMC Network Automation 8.1.

  1. Create a .properties file to use with the upgrade, for example, upgrade_8_2.properties.

  2. Add the multizone containers or container blueprints content from your environment. 
    For example:

    # Place this in the BNA Data folder (i.e. c:\BCA-Networks-Data)
    ############################################################
    # CONTAINER BLUEPRINT INFO
    ############################################################
    #
    # ******************************
    # Multi Zone Container Blueprint
    # ******************************
    #
    # Names of the VFW blueprints either in Firewall Host Blueprints or in
    # Pair blueprints in Multi Zone Container Blueprint.
    #
    # 1. The vfw blueprint name in the key is represented in the form <firewallHostBlueprint>.<vfwBlueprintGuestNodeName>
    #    or as <firewallHostPairBlueprint>.<vfwBlueprintGuestNodeName>
    # 2. The bridged interface names are represented in the form <zoneBlueprintName>.<vfwGuestNodeName>.<interfaceBlueprintName>
    # 3. For the serviced segment names, either the NIC segment blueprint names (port type blueprints in 8.1.x) and/or the address pool name
    #     of the vip segment blueprints (associated with the load balancer pool type blueprint in that zone blueprint) can be provided.
    #
    #    Firewall Host WEB.VFW1
    #             |
    #    Firewall Host Application.VFW2
    #             |
    #    Firewall Host Data.VFW3
    #
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[outside].servicedSegmentNames=Default External Network
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[outside].bridgedInterfaceNames=
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[inside].servicedSegmentNames=Web Pool, Web Network
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[inside].bridgedInterfaceNames=Application.VFW2.outside
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[outside].servicedSegmentNames=
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[outside].bridgedInterfaceNames=Web.VFW1.inside
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[inside].servicedSegmentNames=Application Pool, Application Network
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[inside].bridgedInterfaceNames=Data.VFW3.outside
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[outside].servicedSegmentNames=
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[outside].bridgedInterfaceNames=Application.VFW2.inside
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[inside].servicedSegmentNames=Data Network
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[inside].bridgedInterfaceNames=
  3. Save the file in the BNA Data folder (for example, C:\BCA-Networks-Data)
  4. Continue with the upgrade to 4.0.

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:

Before performing

Review this topic

BMC AR System upgrade

BMC Atrium Core upgrade

BMC ITSM upgrade

BMC SRM upgrade

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:

Before performing

Review this topic

BMC AR System upgrade

BMC Atrium Core upgrade

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 a HA environment, see Installing-products-for-HA.

To prepare for Staged upgrades

In your staging environment, there are two strategies for the staging environment. 

  • Retain the hostname of the staging environment as is. Make sure that the staging setup and the database are in isolated environment. so that they cannot communicate with the production environment (they can only communicate with Zone 1 products). Make sure that the /etc/hosts file of each computer has a load-balancer entry that points to individual computers. Or you can configure the load balancer for the staging environment. Make similar changes on all staged environments. For example, the following is the previous entry in /etc/hosts:

    1.2.3.4   clm-itsm1
    1.2.3.5   clm-itsm

    Update the staging IP and load-balancer IP in /etc/hosts. If you do not plan to use a load balancer, then update /etc/hosts with:

    1.2.3.4   clm-itsm1  clm-itsm

  • Create a staging environment where you modify the application hostnames. For detailed information, see Creating the staging environment. 
    The following lists the correct entry you must make in /etc/hosts, where clm-itsm is the name of the load balancer:

    1.2.3.6   <AR_host_new_name>
    1.2.3.7   <AR_host_load_balancer_name>

     Make sure that the cloning environment is isolated; it should not communicate with production data. Make similar changes on all staged environments. If you do not plan to use a load balancer, then update /etc/hosts with:

    1.2.3.6   <new_AR_hostname>   <Load_balancer_name_if_changed>

To prepare for Staged-Lite upgrades

In a Staged-Lite upgrade, all primary servers are removed from the environment. Make sure that all primary servers services are disabled or suspended on the load balancer. The request should not go to primary servers.

Update the /etc/hosts file of each primary server that you removed so that primary servers and the related load-balancer entry should point to the same IP address.

For example, the following is the previous entry in /etc/hosts:

1.2.3.4   <Cloned_Machine_Hostname>

The following now lists the correct entry you must make in /etc/hosts, where clm-itsm is the name of the load balancer:

1.2.3.4  clm-itsm        clm-itsm

To prepare Enterprise-AR for upgrade

Before you upgrade the Enterprise-AR host, you must complete the following prerequisites:

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

  2. Tune your MS SQL and Oracle databases according to the guidelines in the BMC Remedy AR System documentation: Preparing your database for an upgrade.

To prepare BMC Network Automation 8.1 for the upgrade

Note

These instructions apply to upgrades from 2.1.x to 4.0 if you have existing multi-zone containers or container blueprints in BMC Network Automation 8.1.

  1. Create a .properties file to use with the upgrade, for example, upgrade_8_2.properties.

  2. Add the multizone containers or container blueprints content from your environment.
    For example:

    # Place this in the BNA Data folder (i.e. c:\BCA-Networks-Data)
    ############################################################
    # CONTAINER BLUEPRINT INFO
    ############################################################
    #
    # ******************************
    # Multi Zone Container Blueprint
    # ******************************
    #
    # Names of the VFW blueprints either in Firewall Host Blueprints or in
    # Pair blueprints in Multi Zone Container Blueprint.
    #
    # 1. The vfw blueprint name in the key is represented in the form <firewallHostBlueprint>.<vfwBlueprintGuestNodeName>
    #    or as <firewallHostPairBlueprint>.<vfwBlueprintGuestNodeName>
    # 2. The bridged interface names are represented in the form <zoneBlueprintName>.<vfwGuestNodeName>.<interfaceBlueprintName>
    # 3. For the serviced segment names, either the NIC segment blueprint names (port type blueprints in 8.1.x) and/or the address pool name
    #     of the vip segment blueprints (associated with the load balancer pool type blueprint in that zone blueprint) can be provided.
    #
    #    Firewall Host WEB.VFW1
    #             |
    #    Firewall Host Application.VFW2
    #             |
    #    Firewall Host Data.VFW3
    #
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[outside].servicedSegmentNames=Default External Network
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[outside].bridgedInterfaceNames=
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[inside].servicedSegmentNames=Web Pool, Web Network
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Web.VFW1].interfaceBlueprints[inside].bridgedInterfaceNames=Application.VFW2.outside
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[outside].servicedSegmentNames=
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[outside].bridgedInterfaceNames=Web.VFW1.inside
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[inside].servicedSegmentNames=Application Pool, Application Network
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Application.VFW2].interfaceBlueprints[inside].bridgedInterfaceNames=Data.VFW3.outside
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[outside].servicedSegmentNames=
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[outside].bridgedInterfaceNames=Application.VFW2.inside
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[inside].servicedSegmentNames=Data Network
    containerBlueprints[Multi\ Zone\ Container\ Blueprint].vfwBlueprints[Firewall\ Host\ Data.VFW3].interfaceBlueprints[inside].bridgedInterfaceNames=
  3. Save the file in the BNA Data folder (for example, C:\BCA-Networks-Data)
  4. Continue with the upgrade to 4.0.

Where to go next

Upgrade-sequence

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*