Configuring shared memory, resources, and NPIV

To use IBM LPAR in BMC Cloud Lifecycle Management, complete the remaining shared memory, resources, and N_Port ID Virtualization (NPIV) configuration.

• • To configure the provisioning flow for shared memory or shared processor
  • To configure IBM NPIV

To configure the provisioning flow for shared memory or shared processor

If you want to use a shared memory pool, you must edit the providers.json file for your environment.

• For shared CPU, BMC uses the default shared CPU pool.
• For shared memory, BMC selects the shared memory paging VIOS based on the Access Attribute Value (AAV). The AAV BBSA_LPAR_PRIMARY_VIOS_SELECTION parameter controls the selection of the paging VIOS. Possible values are first and random.
  • If the AAV is set to first, then the first paging VIOS is set by default. Cloud does not set the secondary paging VIOS.
  • If the AAV is set to random, then one VIOS is selected at random and set as the primary VIOS.

1. Open the providers.json file on the computer running the Platform Manager (OSGi) server.
    By default, you can find the providers.json file in the BMCInstallSoftware\BMCCloudLifeCycleManagement\Platform_Manager\configuration folder (Windows) or /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager/configuration (Linux).
2. Search for the BBSA_LPAR_PRIMARY_VIOS_SELECTION parameter.

3. Set attributeValue to first or random.
    For example, the following selection from the providers.json file sets the AAV to first: 

   
     }, {
      "cloudClass" : "com.bmc.cloud.model.beans.AccessAttributeValue",
      "accessAttribute" : {
        "cloudClass" : "com.bmc.cloud.model.beans.AccessAttribute",
        "datatype" : "STRING",
        "guid" : "590ecff8-0cb9-40ca-9a40-65d5736e0c8c",
        "isOptional" : true,
        "isPassword" : false,
        "modifiableWithoutRestart" : false,
        "name" : "BBSA_LPAR_PRIMARY_VIOS_SELECTION"
       },
      "attributeValue" : "first",
      "guid" : "3d650043-958b-4fc6-88e9-40ed9760905c",
      "name" : "BBSA_LPAR_PRIMARY_VIOS_SELECTION"
     }, {
   
4. Save your changes.

To configure IBM NPIV

For NPIV, BMC does not support NPIV zoning and masking configuration. You must create the NSH script in BMC Server Automation that can fetch the World Wide Port Name (WWPN) number with LPAR. After you create the script, you must add parameters to it.

1. Inside BMC Cloud Lifecycle Management, create the NPIV storage compute pool and tag it accordingly.
   1. From the BMC Cloud Lifecycle Management Administration console, click the vertical Workspaces menu on the left side of the window and select Resources.
   2. Under Quick Links on the left, click Compute Pools under the Compute section.
   3. Create the compute pool.
      
      For more information, see:
      • Creating-compute-resource-pools
      • Creating compute resource pools with IBM resources
2. Open the providers.json file on the computer running the Platform Manager (OSGi) server.
    By default, you can find the providers.json file in the BMCInstallSoftware\BMCCloudLifeCycleManagement\Platform_Manager\configuration folder (Windows) or /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager/configuration (Linux).
3. Search for the BBSA_LPAR_NPIV_STORAGE_CONFIG_SCRIPT_NAME parameter.
   BBSA_LPAR_NPIV_STORAGE_CONFIG_SCRIPT_NAME is the NSH script name that you must run as part of SAN and SAN switch configuration.

4. Set attributeValue to the NSH script that configures the SAN and SAN switch.
    For example, the AAV is set here to BBSA_NPIV_Script.nsh. 

   
     }, {
      "cloudClass" : "com.bmc.cloud.model.beans.AccessAttributeValue",
      "accessAttribute" : {
        "cloudClass" : "com.bmc.cloud.model.beans.AccessAttribute",
        "datatype" : "STRING",
        "guid" : "4fd5287f-3941-4f67-bc57-350344599036",
        "isOptional" : true,
        "isPassword" : false,
        "modifiableWithoutRestart" : false,
        "name" : "BBSA_LPAR_NPIV_STORAGE_CONFIG_SCRIPT_NAME"
       },
      "attributeValue" : "BBSA_NPIV_Script.nsh",
      "guid" : "8b0b60d6-50a2-4458-8969-c8695823d736",
      "name" : "BBSA_LPAR_NPIV_STORAGE_CONFIG_SCRIPT_NAME"
     }, {
   
5. Search for the BBSA_LPAR_AUTO_NETBOOT parameter.
   BBSA_LPAR_AUTO_NETBOOT automatically netboots LPAR (if the value is set to true).
    If the value is false, the netboot for LPAR is not not automated; instead you must manually netboot LPAR.

6. Set attributeValue to true (or false).
    For example: 

   
     }, {
      "cloudClass" : "com.bmc.cloud.model.beans.AccessAttributeValue",
      "accessAttribute" : {
        "cloudClass" : "com.bmc.cloud.model.beans.AccessAttribute",
        "datatype" : "BOOLEAN",
        "guid" : "d42d9856-d309-4f79-9ab2-99f6825d39de",
        "isOptional" : true,
        "isPassword" : false,
        "modifiableWithoutRestart" : false,
        "name" : "BBSA_LPAR_AUTO_NETBOOT"
       },
      "attributeValue" : "true",
      "guid" : "afdd419f-f3cf-4572-b0c2-91820c7831ce",
      "name" : "BBSA_LPAR_AUTO_NETBOOT"
     }, {
   

7. Create an NSH script in BMC Server Automation in the Depot\CSM_Scripts folder to perform all the SAN and SAN switch configuration.
    The NSH script name is available from BBSA_NPIV_STORAGE_CONFIG_SCRIPT.
   
   Use the following parameters in your NSH script:

   Parameter name	NSH parameter	Parameter Value	Comments
   SERVER		TARGET.NAME	BMC Server Automation resolves this property with the value [LPAR Name] sent from BMC Cloud Lifecycle Management and executes the script on LPAR.
   LPAR Name (hostname)	$1	VF-LPAR-01
   IP_ADDRESS	$2	xx.xx.xx.xx
   ADAPTER_IDs	$3	1,2,3,4	Comma separated list of adaptor ids.
   WWPNS	$5	ww1:ww2,ww3:ww4,ww5:ww6,ww7:ww8	Comma separated will give the wwpn pairs for each adaptor and further colon separator will give individual wwpn. All in sequence of adaptors.
   DISK_SIZES (MB)	$4	1000.0MB,1500.0MB,500.0MB,1200.0MB	Comma separated list of size for each adaptor in sequence.