Service Pack 1: version 3.1.01

This topic contains information about fixes and updates in this service pack, and provides instructions for downloading and installing the service pack. For information about issues corrected in this service pack, see Known-and-corrected-issues.

Tip

Click here to create a PDF containing only content related to Service Pack 1, including any related patches.

Product versions and compatibility

When you upgrade to Service Pack 1, review the following table for the minimum version requirement for each product and the version each product is upgraded to.

Product	Minimum version required for upgrade	Version upgraded to in Cloud 3.1 SP1	Is Backward compatible?
BMC Server Automation	8.1.02 Patch 001	8.3.00	Yes
BMC Network Automation	8.1.02	8.3.01	No
BMC Atrium Orchestrator	7.6.02.04	7.6.02.06	Yes
BMC Atrium Orchestrator Content	7.6.05	20.13.02	No
BMC ProactiveNet Performance Management	8.6.02	9.0.00	Yes
BMC Remedy AR System Server and BMC Remedy Mid Tier	7.6.04 SP1	8.0.00	Yes
BMC Service Request Management	7.6.04 SP1	8.0.00	No
BMC Atrium Core Web Services	7.6.04 SP2	8.0.00	No
BMC Atrium Core	7.6.04 SP2	8.0.00	No
BMC Remedy IT Service Management	7.6.04 SP1	8.0.00	No
BMC Service Level Management	7.6.04 SP1	8.0.00	No
PXE Server	8.1.02 Patch 001	8.3.00	No
Cloud Portal AR Extensions	2.0	3.1 SP1 (3.1.01)	No
Cloud Platform Manager	2.0	3.1 SP1 (3.1.01)	No
Cloud Database Extensions	2.0	3.1 SP1 (3.1.01)	No

Enhancements

Service Pack 1 provides the following enhancements:

BMC Network Automation 8.3.01 supported

BMC Cloud Lifecycle Management version 3.1.x supports BMC Network Automation 8.3.01 hotfix 6. For details, see KA308017.

BMC Capacity Optimization 9.0 Service Pack 3 supported

BMC Cloud Lifecycle Management version 3.1 Service Pack 1 supports BMC Capacity Optimization 9.0 Service Pack 3.

Support for VMware vCloud Director 5.1

Earlier versions of BMC Cloud Lifecycle Management supported VMware vCloud Director version 1.5 only. This service pack adds support for VMware vCloud Director version 5.1. This enhancement also includes support for the VM shutdown option for VMware vCloud Director.

Networking enhancements

The following table describes the networking enhancements included in this service pack:

Click here to view the table

Enhancement	Description
Ability for administrators to toggle external networks	In previous versions, the Enable and Disable buttons on the Edit Network Containers window did not apply for external networks. With SP1, cloud administrators can now toggle external networks. This capability enables administrators to disable an external network if it is not required.
New warning message when disabling a Cisco Virtual Security Gateway (VSG) firewall	When you disable a VSG firewall node, you are presented with the following message that the VSG VM will be deleted:
Added the virtual LAN (VLAN) ID for Pod-level networks	The VLAN ID is now displayed on the Pod networks table in both the Pods and Network Containers details pane.
Network path validation	For dynamic network containers, the cloud administrator did not know if a network path was still valid after enabling or disabling a distributed firewall. In this service pack, the Status column has been renamed to Enforced on the Network Paths dialog box to indicate if the network path is enforced or not enforced. This capability requires that you are using BMC Network Automation version 8.3.01 hotfix 4. If you are upgrading from version 3.x to 3.1 SP1, BMC recommends that if you are using distributed firewalls in network containers and have network paths present, perform the following procedure to migrate the network paths attached to network containers: Edit the network container. Change to list view. Click Next until you have completed the wizard. Click OK.

New parameter added to specify the Template Disk size

In addition to the affinity settings for the Capacity-Aware Placement Advice (CAPA) service provided by the BMC Capacity optimization integration, you can add a BMCBootDiskSize application parameter to specify the Template Disk size of the virtual machine while defining a service blueprint and creating a Service Offering Instance.

Click here to read more...

The BMCBootDiskSize application parameter specifies the size (in GB) of the Template Disk present in the BMC Server Automation Virtual Guest Package (VGP). The parameter is optional and can be set if you have implemented the BMC Capacity Optimization integration.

In previous versions, the advice provided by BMC Capacity Optimization for the disk present in the VGP was based on the Global Constant value defined in BMC Capacity Optimization. For example, if the disk size in the VGP was 30 GB and the value of the Global Constant defined in BMC Capacity Optimization was 40 GB, then the capacity placement advice was provided as 40 GB for the disk instead of 30 GB. To make the advice more precise, the new BMCBootDiskSize parameter provides administrators with a way to define the value in the service blueprint and in the Add Server option.

Note the following considerations for using the parameter:

If there are multiple disks defined in a Template, this value for the BMCBootDiskSize parameter should be the sum of the sizes of all disks in the Template. For example, if there are two disks in the Template, one 20GB and one 30GB, then set the value to 50.
For a blueprint that has two resource sets, the parameter should take maximum disk size as a value. For example, if there are two resource sets in a blueprint, one with a boot disk size of 20GB and one with 30GB, then set the BMCBootDiskSize parameter to 30
If you do not specify the parameter in the blueprint, the blueprint uses the Global Constant for the Bootdisk defined in BMC Capacity Optimization. The existing blueprints which do no have these parameters need not to be updated.
For Multi-tier SOIs which have multiple Resource sets, the parameter should be the size of the resource set that has the maximum boot disk size.

Note the following limitations:

For the Post-Deploy Action (Transaction Requestable Offering or TRO) Day 2 Add Server operation, the parameter must be specified as a Deployment Parameter Value in the option. For Add Server operations, the Virtual Disk Placement Advice is executed as a Day 1 disk placement advice instead of Day 2 disk placement advice.
The parameter can be specified at the blueprint level, but not at the resource set level.

To configure the BmcBootDiskSize parameter for a blueprint, complete the following steps:

In the Service Blueprints Definition editor, click the Service Definition tab.
Click Parameters.
Click New.
To configure the BmcBootDiskSize parameter for Day 2 Add Server option, open the Options Editor.
Select the Add new server option choice, and then click Option Choice Blueprint Configuration Editor.
In the editor, select Blueprint Configuration > Service Definition > Service Definition > Parameters.
Specify the options for the parameter, and click OK to add the parameter to the blueprint.
In the Option Choice Blueprint Configuration Editor, click OK to save the changes.
Click OK to close the Options Editor.

Resizing an existing disk

For VMware virtual machines (VMs), administrators can add an end-user option to resize the local or system disks that are associated with existing VMs. You can resize the disks using the BMC Cloud Lifecycle Management console. Administrators see Configuring-a-resize-disk-option-choice, and end users see Resizing-an-existing-disk-for-a-VM.

Note

You can define only one Resize Disk option for each service request definition.

Support for multiple placement providers

If multiple placement providers are registered as targets, you can configure the disambiguation rules that identify which placement provider will handle the call. For details, see handle multiple providers as targets.

Version field removed while registering VMware vCloud providers

When you register a new VMware vCloud provider, you cannot view the Version field on the dialog box.

You longer need to provide the VMware vCloud version as BMC Cloud Lifeclycle Management automatically detects the correct VMware vCloud version.

Do you need to install or upgrade to Service Pack 1?

Service Pack 1 for version 3.1 is a full product installation. If you are installing BMC Cloud Lifecycle Management for the first time, install Service Pack 1 for version 3.1 directly.

If you already have BMC Cloud Lifecycle Management installed, upgrade to SP1 for the enhancements or if you require a fix for an issue listed in corrected in version 3.1 SP1.

Before installing or upgrading to service pack 1, consult the Known and corrected installation issues.

Downloading the service pack

For download instructions, see Downloading-the-installation-files.

Download all the files in the BMC Cloud Lifecycle Management 3.1.01 folder.

Installing the service pack as a fresh installation

If you do not already have BMC Cloud Lifecycle Management installed in your environment, perform the procedures in the Installing section using the downloaded files.

Ensure that the supported products are at the latest service pack or patch level listed in the following table. Review especially required hotfixes, for example, KA398011 for BMC Atrium Core.

Required products	Version in 3.1 SP1 installer	Other certified versions
BMC Atrium Core	8.0 – Requires two hotfixes: KA389389 KA398011. Apply to both the enterprise and cloud BMC Remedy AR System servers.)	8.1
BMC Atrium Core Web Registry	8.0	8.1
BMC Atrium Orchestrator Content (cloud-specific content)	3.1 (based on 20.12.04)	None
BMC Atrium Orchestrator Platform, including: BMC Atrium Orchestrator – Configuration Distribution Peer BMC Atrium Orchestrator – Configuration Distribution Peer (High Availability)	7.6.02.06	None
BMC Network Automation, including: (Optional) BMC Network Automation – Device Agent	8.3.01 (Requires the hotfix described in KA398017)	8.3.02 8.5.00 8.5.00
BMC Performance Manager for Virtual Servers	3.0	None
BMC ProactiveNet Performance Management, including: BMC ProactiveNet Central Server BMC ProactiveNet Server BMC ProactiveNet Data Collection Host	9.0.00 (Requires the hotfix described in KA389397.)	9.0.00 SP2 9.5.00
BMC Server Automation, including: BMC Server Automation – Application Server and Console BMC Server Automation – Virtual Center Agent (installed manually) (Optional) BMC Server Automation – PXE Server (Optional) BMC Server Automation – File Server	8.3.00	8.3.01 8.3.02 8.3.03 8.5.00 8.5.00 8.5.00 8.5 SP1 8.5 SP1 patch 2 8.6 patch 1
BMC Remedy Action Request System	8.0.00 (Requires the hotfix described in KA389390. Apply to both the enterprise and cloud BMC Remedy AR System servers.)	8.1
BMC Remedy Mid Tier	8.0.00 (Requires the hotfix described in KA389385.)	8.1
BMC Remedy IT Service Management	8.0.00	8.1
BMC Remedy Service Request Management	8.0.00	8.1
BMC Cloud Lifecycle Management, including: Cloud Database Extensions Cloud Platform Manager Cloud Portal AR Extensions	3.1 SP1

BMC Capacity Optimization compatibility with Cloud 3.1 SP1

The following table lists the versions of BMC Capacity Optimization that are compatible with BMC Cloud Lifecycle Management 3.1 SP1. For more information, see the BMC Capacity Optimization 9.0 home page or BMC Capacity Optimization 9.5 home page.

BMC Capacity Optimization version	BMC Cloud Lifecycle Management version
	2.0	3.0	3.1	3.1 SP1	3.1 SP1 Patch 1
9.0	✅️	✅️	✅️	❌️	❌️
9.0 SP 1	✅️	✅️	✅️	❌️	❌️
9.0 SP 2	✅️	✅️	✅️	❌️	❌️
9.0 SP 3	✅️	✅️	✅️	✅️	❌️
9.0 SP 4	✅️	✅️	✅️	✅️	✅️
9.5	✅️	✅️	✅️	✅️	❌️
9.5 Cumulative Patch 1	✅️	✅️	✅️	✅️	✅️

When you install BMC Cloud Lifecycle Management SP1, the planner fails if you add more than three products during the installation.

Upgrading to the service pack

If you are upgrading from any previous version to version 3.1.01, you must review the items in the Upgrade-considerations topic and complete all the prerequisites for the upgrade to successfully complete the upgrade process. Ensure that the supported products are at the latest service pack or patch level listed in Component-BMC-product-service-pack-and-patch-levels.

You do not need to perform the data migration steps while upgrading from version 3.1 to 3.1.01. You can upgrade your system by performing the steps listed in the Performing-the-upgrade section.

Important

The procedures described in the following upgrading topics apply to upgrading to version 3.1 or upgrading to the latest version 3.1 service pack, unless otherwise specified.

Pre-upgrade tasks

If you are using the existing BMC Cloud Lifecycle Management version 2.1.x, 3.0.x, or 3.1 host to launch the version 3.1 SP1 installation program, then perform the following tasks prior to upgrading:

Uninstall the existing planner version. To uninstall the existing planners, perform the following steps:
- Microsoft Windows: Go to the <Planner Install Directory\UninstallBMCPlanner> folder and run the uninstall.bat file. Example: C:\Program Files\BMC Software\Planner\UninstallBMCPlanner.
- Linux: Go to the <Planner Install Directory/UninstallBMCPlanner> folder and run the uninstall.sh file. Example: /opt/bmc/Planner/UninstallBMCPlanner.
Backup all the installer-related files from the following location:
- Microsoft Windows: c:\windows\temp and %temp% folders
- Linux: \tmp folder
Delete all the uninstall files from both of the above locations.

BMC recommends that you restart the Microsoft Windows computer after performing the pre-upgrade tasks.

Post-upgrade tasks

Apply product hotfixes when you finish the upgrade, for example, KA398011 for BMC Atrium Core.
If you are upgrading from version 3.x to 3.1.01 and you are using distributed firewalls in network containers and have network paths present, BMC recommends that you perform the following procedure to migrate the network paths attached to network containers:
1. Edit the network container.
2. Change to list view.
3. Click Next until you have completed the wizard.
4. Click OK.