Creating the resource group for Infrastructure Management

A high-availability resource group contains the following types of resources:

  • Logical hostname resource—Network address resource, which is an instance of the Logical Hostname built-in resource type.
  • Application resource—High-availability resource, which is an instance of the Infrastructure Management resource type created by using the agent builder.

Perform the following steps to create the resource group.

  1. Create an ordered list of zones for the resource group by entering the following command: clresourcegroup create -n nodeZoneList resource

    The variable nodeZoneList specifies a comma-separated, ordered list of zones for this resource group, and the variable resource specifies the name of the high-availability resource group that you want to create.

    For example:
    clresourcegroup create -n pacific, atlantic pnbmc_rg clresourcegroup show -v pnbmc_rg

    The following output is displayed:
    === Resource Groups and Resources ===
    Resource Group: pnbmc_rg
    RG_description: <NULL>
    RG_mode: Failover
    RG_state: Managed
    RG_project_name: default
    RG_affinities: <NULL>
    RG_SLM_type: manual
    Auto_start_on_new_cluster: True
    Failback: False
    Nodelist: pacific atlantic
    Maximum_primaries: 1
    Desired_primaries: 1
    RG_dependencies: <NULL>
    Implicit_network_dependencies: True
    Global_resources_used: <All>
    Pingpong_interval: 60
    Pathprefix: <NULL>
    RG_System: False
    Suspend_automatic_recovery: False
  2. Add a Logical Host Name Resource to the resource group by entering the following command: clreslogicalhostname create -g resourceGroup -h hostNameList resource

    The variable resourceGroup specifies the name of the resource group in which this resource resides. The variable hostNameList specifies a comma-separated list of Linux/Solaris logical host names by which clients communicate with services in the resource group. The variable resource specifies an optional resource name of your choice.

    For example:
    clreslogicalhostname create -g pnbmc_rg -h artic pnbmc_lg clresource show pnbmc_lg

    The following output is displayed:
    === Resources ===
    Resource: pnbmc_lg
    Type: SUNW.LogicalHostname:2
    Type_version: 2
    Group: pnbmc_rgp
    R_description:
    Resource_project_name: default
    Enabled {pacific}: True
    Enabled {atlantic}: True
    Monitored {pacific}: True
    Monitored {atlantic}: True
  3. Add a Infrastructure Management application resource to the resource group by entering the following command:
    clresource create -g resourceGroup -t resourceType [-p"extension-property [{node-specifier}]" =value ...] [-p standardProperty = value ...] resource

    The variable resourceGroup specifies the name of a high-availability resource group. This resource group must already exist. The variable resourceType specifies the name of the resource type for the resource. The variable standardProperty = value specifies a comma-separated list of standard properties that you set for the resource. The standard properties that you can set depend on the resource type. The variable resource is the name of the resource to add.

    For example:
    clresource create -g pnbmc_rg -t SUNW.pnbmc -p Network_resources_used=pnbmc_lg pnbmc clresource show pnbmc

    The following output is displayed:
    === Resources ===
    Resource: pnbmc
    Type: SUNW.pnbmc:1.0
    Type_version: 1.0
    Group: pnbmc_rg
    R_description:
    Resource_project_name: default
    Enabled {pacific}: True
    Enabled {atlantic}: True
    Monitored {pacific}: True
    Monitored {atlantic}: True

    For example:
    clresource create -g resourceType rg -t _RTRFileName -p Port_list="2638/tcp, 12128/tcp integrationServicePortNumber /tcp" -p Network_resources_used= resourceType lg _resourceType
  4. Tune the Infrastructure Management application resource properties to achieve high-availability by using the following formula:
    Retry_Interval = (Thorough_probe_interval + Probe_timeout) * 2 * Retry_count

    Thorough_probe_interval
    is the time interval that the probe command sleeps. The default is 60 seconds. To account for the time that it takes to bring the BMC TrueSight Infrastructure Management Server up, set this value to 3600 seconds.
    Retry_Count specifies the number of restart attempts. The default is 2. BMC recommends that you set this value to 1 or 0 to achieve efficient high-availability. For the Infrastructure Management application, it is set to 1.
  5. Run the following commands for the Infrastructure Management application to set the Thorough_probe_interval and the Retry_Count values:
    clresource set -p START_TIMEOUT=3600 resourceType
    clresource set -p STOP_TIMEOUT=500 resourceType
    clresource set -p Thorough_probe_interval=600 resourceType
    clresource set -p Retry_Count=1 resourceType

Related topics

Creating and configuring the Infrastructure Management resource type

Configuring Infrastructure Management Server in a cluster

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

Comments