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.

Patch 2 for Service Pack 1: 3.1.01.002

This topic contains information about fixes and updates in this patchand provides instructions for downloading and installing the patch.

Tip

For information about issues corrected in this patch, see Known and corrected issues.

Updates

Patch 2 for BMC Cloud Lifecycle Management 3.1 Service Pack 1 provides the following updates.

Refresh IP address 

In earlier releases of BMC Cloud Lifecycle Management, if the IP address of a virtual machine changed, the IP address in BMC Cloud Lifecycle Management remained unchanged. Now, if the IP address of a VM changes due to any reason such as the IP renewal or DHCP lease expires, the Refresh API detects the change and updates the cloud database with the appropriate IP address.

By default, if the compute container is attached to a load balancer or a firewall, the IP address is not refreshed. You can use the override IP flag to refresh the IP address even if the compute container is attached to a load balancer or a firewall. For more information, see ComputeContainer refreshIP request.

Ability to specify a port range while creating firewall rules

You can now specify a port range while creating distributed or perimeter firewall rules. This enables you to create one firewall rule instead of creating multiple rules for multiple ports.

Note

You must upgrade to BMC Network Automation 8.5 to be able to specify the port range. For more information about BMC Component products version, see Component BMC product service pack and patch levels.

For example, in earlier versions of BMC Cloud Lifecycle Management, if you wanted to block port numbers from 8000 to 8010, then you were required to create 10 firewall rules. In this release, while creating a firewall rule, you can specify a port range from 8000-1010 and all ports in the range are blocked. 

Port Range option button allows you to specify a single port number or a range of port numbers using a dash. For example, 7717-9080. 

The following figure describes the newly added option button. 


For information about creating firewall rules with a port range, see Creating and editing firewall rules.

Ability to specify a disk with a 0GB size

When adding additional disks to a service through a post-deployment action, you can now specify a disk size of 0GB for IBM LPARs. This enables you to create two adapter pairs (WWPN) for multipathing. 

Warning

You can specify 0GB size only for IBM LPAR service offerings. Do not specify 0GB for any other service offerings. 

Simplified disk names

Virtual machine disks will now have display names of Disk1, Disk2,.. Diskn according to the order in which those disks were provisioned. This provides a simpler and clearer view of the disks in the BMC Cloud Lifecycle Management user interface. The original name of a disk is available in the Description field in the CloudDB. You can sort the system disks by the Name field on the Server details screen.

If you want existing disks to benefit from the change in naming, run the DiskRenameUtility.zip after you install the patch. For more information about running the utility, see Configuring after installing the patch

Important

The simplified disk names feature is only applicable for the virtual system disks or local disks. This feature is not supported for Amazon Web Services platform.

Utility to perform cleanup of the reconciliation job runs and events history

In previous releases of BMC Cloud Lifecycle Management, there is no mechanism to clean up the reconciliation job runs and reconciliation job events history records. As the number of records grow, a number of issues occur related to reconciliation jobs used by BMC Cloud Lifecycle Management. To clean up the reconciliation job run and job events history, a .def file is available, with escalation objects.

After you import the file in your environment, you can configure the number of days a record should be maintained in BMC Cloud Lifecycle Management. You can download the utility from the following location: 

ftp://ftp.bmc.com/pub/3101p2/RE_DeleteOldReconRecords.zip

For more information, see Performing clean up of reconciliation job runs and events history.

Downloading the patch

For download instructions, see Downloading the installation files

Supported upgrade paths 

The following table describes the supported upgrade paths if you want to install BMC Cloud Lifecycle Management version 3.1.01.002. If your current version is 3.1, you need to upgrade to 3.1 SP1 to install Patch 2.

Current version Upgrade support
3.1 or earlier Upgrade to 3.1 Service Pack 1 (3.1.01)
3.1.01

Patch installer installs 3.1.01 Patch 1 and Patch 2 together

Tip

You can consult the Known and corrected issues table to view the issues that are resolved in Patch 1 and 2.

3.1.01.001 Patch installer installs 3.1.01 Patch 2

Preparing to install the patch

The following table describes the steps you need to perform before installing this patch. 

Step Procedure
1. Upgrade to BMC Cloud Lifecycle Management 3.1.01 before upgrading to patch 2. 
For more information about upgrading, see Upgrading.
2. Ensure that the supported products are at the latest service pack or patch level. 
For more information about the supported product versions, see Component BMC product service pack and patch levels.
3.

If you are installing patch 2 on BMC Cloud Lifecycle Management 3.1.01, then perform the steps 3.1-3.4 before installing this patch.

Note

Skip the steps if you have already installed Patch 1.  

3.1

(Optional) Install only if you require the fix for QM001790410, else, skip to step 3.2.

Note

QM001790410: Issues with SOI provisioning rollback behavior cause problems such as improper clean up of VMs from the infrastructure or IP address conflicts.

Upgrade BMC Server Automation to version 8.3 Service Pack 2 and then apply the hotfix. Contact BMC Customer Support to obtain the hotfix.

  Perform the following steps to install the hotfix on BMC Server Automation version 8.3 Service Pack 2
  1. Apply the latest hotfix applicable to BMC Server Automation 8.3 Service Pack 2. Contact BMC Customer Support to obtain the latest hotfix.
  2. Log on to BMC Server Automation Console as a BLAdmin user.
  3. Distribute the configuration object with version 83010118 on the SCVMM Hyper-v Server.
    After the distribution is complete, you can access the standard switch in the REST response.
  4. Verify whether the hotfix is applied successfully by accessing the following sample REST URI:
    https://localhost:9843/group/Servers/Vmware/SCVMMHyper-vServerName/Assets/BMC_SCVMM/BMC_SCVMM_Cloud/?username=BLAdmin&password=PASSWORD&role=BLAdmins

    An added attribute, Host Standard Switches, which contains the comma-separated values of the standard switches, is visible.
 3.2

(Perform this step only if you have skipped step 3.1)

Install the hotfix for BMC Server Automation 8.3 from the following location.

 ftp://ftp.bmc.com/pub/CLM3.1SP1HF3/scvmm.zip

  Perform the following steps to install the hot fix on BMC Server Automation version 8.3
  1. Take a snapshot of the BMC Server Automation server and back up the associated database.
  2. Log on to BMC Server Automation Console as a BLAdmin user.
  3. From the Configuration menu, select the Config Object Dictionary View check box.
  4. In the Config Object Dictionary tab, click Add Configuration Object and import the configuration object.
  5. Select Server Object and then select the scvmm.zip file as the implementation file. 
    This imports the System Center Virtual Machine Manager (SCVMM) configuration object in the BMC Server Automation 8.3 application server.
  6. Distribute the configuration object with version 83010118 on the SCVMM Hyper-v Server.
    After the distribution is complete, you can access the standard switch in the REST response.
  7. Verify whether the hotfix is applied successfully by accessing the following sample REST URI:
    https://localhost:9843/group/Servers/Vmware/SCVMMHyper-vServerName/Assets/BMC_SCVMM/BMC_SCVMM_Cloud/?username=BLAdmin&password=PASSWORD&role=BLAdmins

    An added attribute, Host Standard Switches, which contains the comma-separated values of the standard switches, is visible.
3.3

If you have changed the administrator user password for the enterprise AR System and cloud AR System after the last time you installed BMC Cloud Lifecycle Management, you must ensure that the passwords match the installation configuration file. 

If the passwords do not match, the installation fails. 

  Perform the following steps to ensure that the passwords match
  1. Generate an encrypted password: 
    1. On the Cloud Platform Manager, go to C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Utilities.
    2. Run the BMCCloudLifeCycleManagementMaintenanceTool.bat/sh file.
    3. Click Encrypt.
    4. In the Password and Confirm Password fields, enter the new password.
    5. Click Encrypt.
    6. Copy the new encrypted password.
  2. Update the encrypted password in the installation configuration file on the enterprise AR System: 
    1. Go to InstallationDirectory\BMCCloudLifeCycleManagement\ and open theBMCCloudLifeCycleManagementInstalledConfiguration.xml file.
    2. Search for the BMC_AR_PASSWORD_HOSTING attribute.
    3. In the value field for the attribute, enter the encrypted password.
  3. On the cloud AR System server, follow the same steps to update the encrypted password in the installation configuration file.  
3.4

Take a VM snapshot and a database backup of the enterprise AR System server, cloud AR System, Platform Manager, and BMC Atrium Orchestrator. 

Installing the patch can affect the AR objects in a non-overlay mode. Ensure that you follow the best practices for customizations.

4.

Ensure that JAVA_HOME variable is set on the servers where you are installing the patch. On Linux servers, ensure that X11 libraries are installed.

Installing the patch

This topic describes the procedure to install patch 2.

Note

For installing patch 2 on Cloud Express, place the installer file on the host and extract the files. Perform step 2 to install the patch 2.

To install patch 2: 

  1. Download and extract the installer and place a copy on each of the VMs that have the following components installed:
    1. Enterprise BMC Remedy AR System server
    2. Cloud BMC Remedy AR System server
    3. Cloud Platform Manager

    4. BMC Atrium Orchestrator Platform

      Notes

      Install patch 2 on the components in an incremental manner. Install patch 2 on the enterprise BMC Remedy AR System first, then on cloud AR System server, then Platform Manager, and finally on BMC Atrium Orchestrator Platform server.

      For Linux, extract the installer by using the tar –xvf CLMPatchInstaller3101P2.tar.gz command.

  2. On the Enterprise AR System server, install patch 2: 
    1. Start one of the following installation programs:
      • On Microsoft Windows, double-click the setup.cmd file. 
      • On Linux, navigate to the \CLMPatchInstaller\Disk1 location and run the setup.bin file by using Xmanager.

        With Xmanager, X applications installed on remote UNIX-based computers run seamlessly with Windows applications side by side.

        Note

        You can also use VConsole to launch the installer.

    2. On the Welcome pane, note the warnings and click Next
    3. On the Directory selection pane, navigate to the location on the host where you want to install the BMC Cloud Lifecycle Management patch installer files and click Next.
      You can accept the default value if you do not have a specific location for the installation files.
    4. On the Installation Preview pane, review the summary and click Next
  3. Repeat step 2 on the Cloud AR System server. 
  4. Repeat step 2 on the Cloud Platform Manager
  5. Repeat step 2 on the server where BMC Atrium Orchestrator Platform is installed. 
  6. (Optional; only if you have a high availability environment) For a BMC Cloud Lifecycle Management high availability environment, perform the following steps:
    1. On each additional or secondary enterprise AR System server, copy all files from the <CLMPatchInstaller>\files\ear\P2\jars\Cloud_Portal\plugin and replace them in the <BMCCloudLifeCycleManagementInstallationDirectory>\Cloud_Portal\plugin location.
    2. On each secondary BMC Atrium Orchestrator Configuration Distribution Peer, copy all files from the <CLMPatchInstaller>\files\ao\P2\nsh location and replace them in the <NSH Installation Directory>\scripts location.
    3. If you have installed the NetApp Storage adapter version 20.12.02, copy the jar files from the <CLMPatchInstaller>\files\ao\P2\adp\jars location and replace them in the <AO-CDP InstallationDirectory>\server\grids\<GRID NAME>\library\adapters\implementations\bmc-adapter-netapp-storage-actor_20.12.02.00_1 directory.

Configuring after installing the patch

The following table describes the steps you need to perform after installing this patch.

Step Procedure
1.

Run the DiskRenameUtility utility to apply the simplified disk names update for the existing disk names.

Before running the utility, ensure that:

  • Enterprise AR system server and the cloud AR System server are running
  • DSO and reconciliation is working on both the servers.
  Perform the following steps to run the utility
  1. Download the DiskRenameUtility.zip file from the following location and place it on the Cloud AR system server.
    ftp://ftp.bmc.com/pub/3101p2/DiskRenameUtility.zip 
  2. Extract the zip file and navigate to the workfolder directory and update the utility.properties file to run in any of the modes that suits your requirement.
    For more information about the available modes, see the Available modes for the utility.properties section below. 
  3. Set the JAVA_HOME in the environment variable.
  4. (Windows) While logged on as an Administrator, open a command prompt and type:
    C:\workfolder>run.bat
    (Linux) Provide execute permission to the run.sh script and then run the utility:
    chmod 755 run.sh
    ./run.sh
  Available modes for the utility.properties file

To run the DiskRenameUtility, you must configure the utility.properties file to run in a suitable mode. You can configure the following modes in the utility.properties file:

Mode name Description
Print

In Print mode, the utility captures the details of disks present in the environment with their current names and the proposed new names. You can view the report by opening the output.html file from workfolder directory.

To specify this mode, set the PrintFlag=1.  

Output (Default mode) After verifying the report, you can run the utility in the output mode, by setting the PrintFlag value to 0. Running the utility in output mode renames the disks to new name format.

To specify this mode, set the PrintFlag=0

If no values are specified, the utility runs in the output mode.

Rollback 

In the Rollback mode, the changes made to the disk names are reverted to the original disk names.

  • 1 – Enable rollback mode
  • 0 – disable rollback mode (default)
Optional

In the Optional mode, you can also run the utility against a specific VM by specifying the VirtualguestNames property.

 For example, VirtualguestNames= vg1;vg2;vg3; 


2. Clear the mid-tier cache.
If the mid-tier used by the BMC Cloud Lifecycle Management console is different than the mid-tier running on the enterprise AR System server, then you need to clear the cache. 
  1. Log on to the Mid Tier Configuration Tool. 
  2. Perform a flush cache.
    The flush cache removes all items from the caches that BMC Remedy Mid Tier maintains. The next time the mid tier needs those objects, the most up-to-date versions are retrieved from the AR System server. 
3. Clear the browser cache.
4.

Delete the mid-tier cache.

  Perform the following steps to hard delete the mid-tier cache
  1. Stop the MidTier service.
  2. Clear contents of the following folders:

    <BMC Software>\ARSystem\midtier\cache
    <BMC Software>\ARSystem\midtier\PluginsCache
    <Apache Software Foundation>\Tomcat6.0\work

  3. Restart the MidTier service.

Related topics

Downloading the installation files

Known and corrected issues

Was this page helpful? Yes No Submitting... Thank you

Comments