Patch 3 for Service Pack 1: 3.1.01.003

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

Tip

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

Click here to create a PDF version of the Patch 3 release notes.

Updates

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

Support for dedicated pod-level networks in container reprovisioning

Whenever you create new networks in a pod in BMC Network Automation, these networks must be synchronized in BMC Cloud Lifecycle Management for them to be visible and to be able to provision to the new networks. For dedicated pod-level networks existing containers must be reprovisioned with the new node in order to be provisioned to the dedicated pod-level network. For details, see Synchronizing network pods, Reprovisioning network containers and Example of container reprovisioning - adding a new NIC.

Pod synchronization propagates newly-added networks in the pod to all the existing network containers

The pod synchronization operation now propagates newly-added networks in the pod to all the existing network containers. These newly-added pod-level networks can be used in existing containers. A new attribute, propagateNetworkChangesToContainers (as shown in the following code snippet) has been added to the providers.json file to control this behavior:

Click here to view a snippet of the providers.json file that shows this attribute.

{

"cloudClass" : "com.bmc.cloud.model.beans.AccessAttributeValue",

"accessAttribute" : {

"cloudClass" : "com.bmc.cloud.model.beans.AccessAttribute",

"datatype" : "BOOLEAN",

"description" : "If flag is set to true, POD synch changes like addition of new
POD network, are propagated to all associated containers.Default value is true",

"guid" : "f520a1c8-ea13-41cb-b01f-ef8df104a04f",

"isOptional" : true,

"isPassword" : false,

"name" : "propagateNetworkChangesToContainers"

"attributeValue" : "true",

"guid" : "5b44f92e-2599-4890-9608-ae5c99591f96",

"name" : "propagateNetworkChangesToContainers"

}

Support for an organization administrator to configure vCloud provider

You can register the vCloud provider with the organization administrator user account. For details, see Registering VMware vCloud providers.

Support for NPIV storage as a Day 2 operation

BMC Cloud Lifecycle Management now supports adding additional storage as a Day 2 operation using NPIV.

Support for adding new networks in a pod

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.003. If your current version is 3.1, you need to upgrade to 3.1 SP1 to install Patch 3.

Current version	Upgrade support
3.1.01.002	Patch installer installs 3.1.01 Patch 3
3.1.01.001	Patch installer installs 3.1.01 Patch 2
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 or earlier	Upgrade to 3.1 Service Pack 1 (3.1.01)

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 3. 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 3 on BMC Cloud Lifecycle Management 3.1.01, then perform the steps 3.1-3.6 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 Apply the latest hotfix applicable to BMC Server Automation 8.3 Service Pack 2. Contact BMC Customer Support to obtain the latest hotfix. Log on to BMC Server Automation Console as a BLAdmin user. 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. 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	(Optional) Perform this step only if you have a Hyper-V environment and 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 Take a snapshot of the BMC Server Automation server and back up the associated database. Log on to BMC Server Automation Console as a BLAdmin user. From the Configuration menu, select the Config Object Dictionary View check box. In the Config Object Dictionary tab, click Add Configuration Object and import the configuration object. 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. 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. 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	(Optional) If your environment has LPAR setup with NPIV, and you would like to create Day 2 “Additional Disks” via NPIV, apply the BMC Server Automation 8.3.00 Hotfix #163. Please contact BMC Support to obtain the hotfix. Perform the following steps to install the hot fix on BMC Server Automation version 8.3. Take a VM snapshot of the BMC Server Automation server and backup of associated Database. Download the ibmframe.zip file to the computer on which BMc Server Automation is installed. Log in to the BMC Server Automation Console with BLAdmin privilege. Go to Configuration menu and select the Config Object Dictionary View option. Click the Add Configuration Object (Green Plus) icon in the upper right corner of the Config Object Dictionary tab. Select Server Object and click Next. On the Implementation.zip File window, browse and select ibmframe.zip, click Next, and then Finish. Once the CO import is complete, run a Distribute Configuration Objects job to distribute the above imported CO with version 83030001 on the AIX Proxy Server configured in IBM Frame.
3.4	(Optional) Upgrade to BMC Network Automation 8.5.01 version only If you need the fix for QM001829459 (NAT using a private IP address range). If you skipped upgrading to BMC Network Automation 8.5.01, BMC Network Automation 8.3.01 Hotfix #39 is required. Install the hotfix for BMC Network Automation from the following location: ftp://ftp.bmc.com/pub/bna-8.3.01-hotfix39.zip. Perform the following steps to install the hot fix on BMC Network Automation version 8.3. Download and extract bna-8.3.01-hotfix39.zip. Stop the BNA Service. Take a backup of the bca-networks.war file from the $\BMC Software\BCA-Networks\tomcat\webapps folder. Copy bca-networks.war from the extracted location and replace it in the $\BMC Software\BCA-Networks\tomcat\webapps folder. Start the BNA Service.
3.5	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 Generate an encrypted password: On the Cloud Platform Manager, go to C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Utilities. Run the BMCCloudLifeCycleManagementMaintenanceTool.bat/sh file. Click Encrypt. In the Password and Confirm Password fields, enter the new password. Click Encrypt. Copy the new encrypted password. Update the encrypted password in the installation configuration file on the enterprise AR System: Go to InstallationDirectory\BMCCloudLifeCycleManagement\ and open the BMCCloudLifeCycleManagementInstalledConfiguration.xml file. Search for the BMC_AR_PASSWORD_HOSTING attribute. In the value field for the attribute, enter the encrypted password. On the cloud AR System server, follow the same steps to update the encrypted password in the installation configuration file.
3.6	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 the 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 3.

Note

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

To install patch 3:

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 3 on the components in an incremental manner. Install patch 3 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 CLMPatchInstaller3101P3.tar.gz command.
On the Enterprise AR System server, install patch 3:
1. Start one of the following installation programs:
  - On Microsoft Windows, double-click the setup.exe 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.
Repeat step 2 on the Cloud AR System server.
Repeat step 2 on the Cloud Platform Manager.
(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\Px\jars\Cloud_Portal\plugin and replace them in the <BMCCloudLifeCycleManagementInstallationDirectory>\Cloud_Portal\plugin location.
  
  Note
  In the above path, x refers to the patch number. Therefore, to refer to the path for patch 3, specify <CLMPatchInstaller>\Disk1\files\patch\ear\P3\jars\Cloud_Portal\plugin.
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.
On the server where BMC Atrium Orchestrator Platform is installed, perform the following steps to install the patch manually:
1. Copy the adapter-netapp-storage-20.12.02.00.jar file from <CLMPatchInstaller>\files\patch\ao\P2\adp\jars\ to the<BMC Software>\AO-Platform\CDP\server\grids\<Grid-Name>\library\adapters\implementations\bmc-adapter-netapp-storage-actor_20.12.04.00.03_1 directory.
2. Copy all the files from <CLMPatchInstaller>\files\patch\ao\P2\nsh to <BMC Software>\BladeLogic\NSH\scripts\.
3. Login to the Grid Manager, go to Applications > Repository Manager, and then upload the .roar files from <CLMPatchInstaller>/files/patch/ao/P2/roar.
4. Activate the latest roar modules on the Grid Manager.

Configuring after installing the patch

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

Step

Procedure

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

Download the DiskRenameUtility.zip file from the following location and place it on the Cloud AR system server.
ftp://ftp.bmc.com/pub/3101p3/DiskRenameUtility.zip
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.
Set the JAVA_HOME in the environment variable.
(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;

Apply the ITSM fix located at: <CLMPatchInstaller>\Disk1\files\patch\itsm\CM_8000_2014FEB17_SW00412654_ALL.

Refer to the CM_8000_2014FEB17_SW00412654_ALL.docx file in the preceding path for the steps to apply the fix.

Copy the BSH files located at: <CLMPatchInstaller>\Disk1\files\patch\bna into the BCAN_DATA directory of the BMC Network Automation server. (Default) C:\BCA-Networks-Data. This step is required to add new pod-level networks. Refer to the readme.txt file in the preceding path for the usage of the scripts.

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.

Log on to the Mid Tier Configuration Tool.
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.

Clear the browser cache.

Delete the mid-tier cache.

Perform the following steps to hard delete the mid-tier cache

Stop the MidTier service.
Clear contents of the following folders:
<BMC Software>\ARSystem\midtier\cache
<BMC Software>\ARSystem\midtier\PluginsCache
<Apache Software Foundation>\Tomcat6.0\work
Restart the MidTier service.

Troubleshooting patch installation

In case you have any problems installing this patch, contact BMC Support with the logs\clmpatchinstaller_install_log.txt and PatchApplicationTracker.txt files located in the <CLMPatchInstallation> directory.