Launching the upgrade and pre-analyzing the currently installed products

This topic describes how to launch the upgrade installer and pre-analyze the currently installed products to ensure a successful upgrade.

Before you begin

  1. Make sure that no other BMC products are installed are on the installer host. Start with a clean environment. 
  2. Review carefully the upgrade considerations and prerequisites described in Preparing for upgrades.
    The information listed in this topic is absolutely crucial for a successful upgrade.  
  3. Log on to the computer as the user provided in the installer and verify the user's profile. 
    If you do not verify this information, the product installations probably will not launch properly. For example: 
    • Windows – If the user is Administrator, the profile must be C:\Users\Administrator
    • Linux – If the user is root, the profile must be /root

  4. (Windows only) Stop and disable both the IP Helper and Windows HTTP Proxy web service on the target hosts before you start installation. Otherwise, the installations fail.

To launch the upgrade installer

Note

  • Accept the default values in the installer unless you have a good reason to change them.
  • Do not mix and match IP addresses and host names during product selection in the Host Information panel. Enter all IP addresses or all host names, but do not combine them. 
  • To avoid problems if the VLAN and IP addresses of the hosts are changed, use host names. Any underlying changes to the VLAN or IP addresses are then transparent.
  1. Download the BMC Cloud Lifecycle Management solution, as instructed in Downloading the installation files.
  2. To start the installer, perform the following steps based on your operating system:

    1. (Windows) From the command prompt, go to Planner > Windows > Disk 1.

    2. (Linux) From the shell prompt, go to Planner\Linux\Disk1.
      On Linux, launch the installer by using Xmanager to start the ./setup.sh command. 
      With Xmanager, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.

      Tip

      You can also use vConsole or Xming to launch the installer.

      Ensure that the current directory is Planner\<operating _system>\Disk1 before you launch the installer.

  3. On the Welcome page, click Next
  4. Review the license agreement, click I agree to the terms of license agreement, and click Next.
  5. On the Installation Prerequisites panel, review all the prerequisites that you must complete before you start the installation.
  6. Select the I have read the prerequisites check box and click Next.
    (Optional) Select the Do not display this panel for subsequent installations check box if you do not want to view the prerequisites again during other product installations.

    Note

    If you have not completed any of the prerequisites listed on the Installation Prerequisites panel, exit the installer and complete the steps first.

  7. On the Directory Selection panel, navigate to the location on the host where you want to install the planner and click Next.
  8. The default value is C:\Program Files\BMC Software\Planner) (Windows) or /opt/bmc/Planner (Linux). Otherwise, navigate to the directory where you want to place the installation files.
  9. On the Installation Preview panel, review the information and click Install.
  10. On the NSH panel, review the installation location, and then click Next
    The default location is C:\Program Files\BMC Software\NSH for Windows or /opt/bmc/Planner/NSH for Linux. Otherwise, navigate to the directory where you want to install NSH. 
  11. In the Select Installation Type panel, select Upgrade and then click Next.
  12. In the Integrate Disclaimer Information panel, review the guidance.
    Make sure that upgrading does not impact your customizations or your system performance.
  13. Click I agree to the terms of the disclaimer, and then click Next

  14. On the Select Deployment Template panel, choose the type of deployment template that matches your environment.
    • Compact Deployment – For installations on a single host.
    • Small Deployment – For managing up to 10,000 devices (virtual or physical).
    • Medium Deployment – For managing up to 25,000 devices (virtual or physical).

      Note

      In version 4.6, only Compact, Small, and Medium deployments are supported.

  15. In the BMC AR System Configuration panel, the installer asks if you use one or more AR System servers in your environment.
    If you had Compact Deployment or RDS stacks, you would select Yes, I have only one BMC AR System server. If you were running an older version of BMC Cloud Lifecycle Management, you would No (I have an Enterprise-AR and a Cloud-AR server).
  16. Click Next.
  17. If you select Small or Medium Deployment, the Deployment Tier Selection panel appears. (This panel does not appear with Compact Deployment, because the products are installed only on the Control Tier.)

  18. In the Deployment Tier Selection panel, select the correct option to upgrade your environment, and click Next.
    Your options are:

    • Control Tier
    • Workload Tier
    • Both (detault)

    The Host Information panel appears for the Control Tier. 

  19. Click Next.
    The Host Information panel appears.

To upgrade and pre-analyze the currently installed products

As part of the upgrade process, the installer runs a utility that pre-checks your environment and generates an HTML report that checks your environment and lists recommendations to fix it.

  1. Review the products in the Control and Workload deployment tiers.
  2. Enter a valid host name for each installed product that you want to upgrade.
    You do not need to fill out the entire form; leave the Host Name field empty if the product is not currently installed in your environment. Products that you can upgrade across geographical locations or for high availability (HA) display a plus sign (+) next to them. To add additional products, select Add a Node. You can also delete the host by selecting Delete this node.
    Ping the target hosts to make sure that they are valid. You can also enter IP addresses. But do not mix and match host names and IP addresses. Enter one or the other, but not both. To avoid problems if the VLAN and IP addresses of the hosts are changed, use host names. Any underlying changes to the VLAN or IP addresses are then transparent.

    Note

    You can enter the target hosts before you start upgrading. Only required products were selected. If necessary, you can upgrade products in multiple sessions.

  3. Click Next.
    The installer validates the target hosts, to ensure a successful integration. 

  4. Enter the operating system user names and passwords for each host in your deployment. 
    To use the same credentials and passwords for each host, select the Apply the same credentials check box. The installer validates the credentials, deploys the RSCD Agent on the target hosts, and performs additional installation actions. 

    Note

    Deployment is much faster if the installer host and the target host are in the same subnet (about 3 minutes per VM). Otherwise, this step can take quite a long time to complete. Depending on your environment, deploying the RSCD agents can take up to an hour to install per VM if you are installing across the WAN.

  5. Click Next to continue.
    The Pre-Analyzer uses the OS credentials to verify the administrator privileges. The installer deploys the BMC BladeLogic Remote System Call Daemon (RSCD) Agent on the target hosts if it is not present. 

    Deploying the RSCD Agent and copying the installer files to the target hosts can take an extended period of time to perform. 
  6. When the Pre-Analyzer Product Information Panel appears, click each product tab and enter the missing inputs for each target host. 
    For example, enter the database passwords and the other missing inputs for the BMC AR System - Cloud Portal Database - Primary target host.  
     
  7. Click Next to execute the Pre-Analyzer.
  8. When the Pre-Analyzer Execution Report appears, review the report card of your current installed environment. 
    The HTML report provides a high-level overall status of the target servers. As you can see from this report, most of the target servers from the 3.1 environment failed. 
     
  9. Click the link to view a detailed report of the problems in your environment. For a detailed PreAnalyzer Execution Report, see PreAnalyzer checks.

    Note

    The report lists both the reasons why your target server failed the pre-analyzer check and the suggested remediations. If one or more of the target servers fail the pre-analyzer check, you must fix the underlying problems before you can continue with the upgrade. 


     

  10. When all the target servers have passed the pre-analyzed check, click Next to continue. 
  11. Review the PreAnalyzer Validation panel and then click Next
    The PreAnalyzer phase is finished and you are now ready to start upgrading the products in your deployment.
  12. When the deployment confirmation panel appears, carefully review the summary of the host settings.
    Make sure that the products are installed on the correct target hosts.
    To change the hosts, click Previous. You cannot modify the configuration after you start the installation.
     
  13. (Optional) Non-installer step: Track the progress of the installation (for example, verify whether the installation files are copied to the target host) as explained in Tracking installation progress.
  14. Click Next.
    The Installation Progress panel appears. The installer stages products into the Currently Installing and Upcoming Installs trees, and automatically selects the correct product to install in its proper order.

    Currently Installing

    Product does not depend on other products to install, for example, BMC AR System Server - Cloud Portal and Database - Primary.

    Upcoming Installs

    Product depends on other products being installed first. For example, before you can install Platform Manager - Cloud Portal, you must finish installing BMC Atrium Orchestrator Server. Other possible tasks include configuring Data Execution Prevention (DEP) to run the executable. As a result, products that have an unmet dependency remain in the Upcoming Installs tree until the installation of the product on which they depend is complete.

    Tip

    You can review the current progress of an installation at any time by selecting the product in the Currently Installing tree. Click View Deployment Status to review previous progress.

  15. Select a product from the Currently Installing tree (for example, BMC AR System Server - Cloud Portal and Database - Primary) and click Next.

    Tip

    Do not forget to take a snapshot of your VM or back up your database when the installer prompts you.

  16. At the prompts, enter the installation inputs for each product from your planning spreadsheet.
    After you have entered the required setup information, the installer runs a validation check of your user inputs and the Installation Preview panel is displayed.
  17. Click Install.
    The installer displays the status of the installation after the installation is completed. Resolve any warning messages before you continue.
  18. Click Next to continue installing the remaining products in the solution. Otherwise, click Exit to exit the installer.
    After you exit the installer, you can resume installing remaining products at any time. If needed, you can switch installer computers. 

    Tip

    To immediately resume installing other products in the solution after you exit the installer, launch the installer and choose Modify Existing Deployment.

  19. After you complete the installation session, click Done and then review the summary.
  20. Click Next
  21. Perform one of the following actions:
ActionSteps
Resume installation by modifying the existing deployment
  1. Select Modify Existing Deployment (the default).
  2. Click Next to continue installing the remaining products in the solution.
  3. After you complete an installation, create a snapshot of the host computer before continuing with the rest of the installation process.
Exit the installation
  1. Select Exit the installation. 
  2. Click Next if you are finished. 
  3. Click Done to exit the installer.
    After you exit the installer, you can resume installing remaining products at any time. 
  4. To resume installing other products in the solution after you exit the installer, launch the installer and choose Modify Existing Deployment
  5. After you complete an installation, create a snapshot of the host computer before continuing with the rest of the installation process.

Where to go from here


  • Apply the following hotfixes after you install or upgrade version 4.6.00:

    • 000110488: This hotfix provides missing files necessary for using a currency other than USD.
    • 000100373: This hotfix is required if you have BMC TrueSight Capacity Optimization deployed in your environment.
    • 000113716: This hotfix is required for BMC Network Automation



  • Apply the following hotfixes after you install or upgrade version 4.6.03:

    • 000113706: This hotfix is required if MyIT 3.1 is deployed in your environment.

    • 000100716: This hotfix is required if BMC Network Automation 8.7 is deployed in your environment.

    • 000113716: This hotfix is required if BMC Network Automation 8.8 is deployed in your environment.

  • If you encountered any errors during the installation, see troubleshooting installation issues.
  • If you want to install the products from another computer, see switching installer computers.
Was this page helpful? Yes No Submitting... Thank you

Comments