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:
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
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 details, see Synchronizing network pods and Editing 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. |
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: |
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. |
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). |
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. |
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:
- Enterprise BMC Remedy AR System server
- Cloud BMC Remedy AR System server
Cloud Platform Manager
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:
- 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.
- On the Welcome pane, note the warnings and click Next.
- 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. - On the Installation Preview pane, review the summary and click Next.
- Start one of the following installation programs:
- 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:
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.
- 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.
- 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:
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.
Copy all the files from <CLMPatchInstaller>\files\patch\ao\P2\nsh to <BMC Software>\BladeLogic\NSH\scripts\.
Login to the Grid Manager, go to Applications > Repository Manager, and then upload the .roar files from <CLMPatchInstaller>/files/patch/ao/P2/roar.
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 |
---|---|
1. | Run the DiskRenameUtility utility to apply the simplified disk names update for the existing disk names. Before running the utility, ensure that:
|
2. | 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. |
3. | 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. |
4. | 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.
|
5. | Clear the browser cache. |
6. | Delete the mid-tier cache. |
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.
Related topics
Downloading the installation files
Comments
Log in or register to comment.