InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - Solaris

LDomName

The name of the LDom that you want to monitor.

Type-dimension: string-scalar

Default: n/a

Example: "ldom1"

CfgFile

The absolute path of the XML file that contains the LDom configuration. To create the configuration file for an LDom, run the following command:

$ ldm list-constraints -x ldom_name > ldom_name.xml

If this attribute is configured, LDom agent uses this file to create an LDom only when LDom configuration is not found on a node. Make sure that default services like virtual disk server (vds), virtual switch service (vsw), and virtual console concentrator service (vcc) are already created on all the nodes to use the xml file.

If domain migration is planned for the LDom, then this attribute must be configured.

Refer to the ldm(1M) manual page for information on this file.

The configuration file must be present locally on all of the systems or on a shared disk where it is accessible by all of the systems.

Type-dimension: string-scalar

Default: n/a

Example: "/root/ldom-cfg/ldom1.xml"

MonitorCPU

Specifies whether the LDom agent monitors the CPU usage of the LDom.

If the CPU usage of all of the VCPUs attached to the LDom is equal to either 0% or 100%, then the resource is declared FAULTED.

For an LDom with one VCPU, set this attribute to 0. This setting is to work around an LDom limitation where an LDom with one VCPU always reports 100% CPU usage.

Type-dimension: boolean-scalar

Default: 0

NumCPU

The number of virtual CPUs that you want to attach to the LDom when it is online. If you set this attribute to a positive value, the agent detaches all of the virtual CPUs when the service group goes offline. Do not reset this value to 0 after setting it to 1.

If the agent's monitor entry point finds that the CPUs available to the LDom is less than the value of the NumCPU attribute, it logs a warning about the mismatch. It also sets ConfidenceMsg and ConfidenceLevel accordingly.

This attribute can be modified while LDom is online to dynamically reconfigure virtual CPUs assigned to the LDom.

Type-dimension: integer-scalar

Default: 0

Example: 16

Memory

The amount of memory to be assigned to an LDom.

The expected value of this attribute is a positive integer followed by the unit G, M, or K, where G stands for gigabytes, M stands for megabytes, and K stands for kilobytes. The memory specified here is governed by the --auto-adj option of the ldm set-memory command which enforces it to 256 megabyte alignment.

The success of the ldm set-memory command depends on the availability of the memory pool that is free.

If the agent's monitor entry point finds that memory available to the LDom is less than the value of the Memory attribute, it logs a warning about the mismatch. It also sets ConfidenceMsg and ConfidenceLevel accordingly.

This attribute can be modified while LDom is online to dynamically reconfigure memory assigned to the LDom.

Type-dimension: string-scalar

Default: Null

Example 1: 4G

Example 2: 2048M

ConfigureNetwork

Specifies if the LDom agent configures the network-boot-arguments PROM variable of the logical domain. If the value of the attribute is set to 1, then the LDom agent updates the network-boot-arguments PROM variable using the following attributes: IPAddress, Netmask, Gateway, and DNS.

Type and dimension: integer-scalar

Default: ""

IPAddress

During the online operation, the agent sets the value of this attribute to the host-ip key of the network-boot-arguments PROM variable of the LDom.

Type and dimension: string-scalar

Default: ""

Netmask

During the online operation, the agent sets the value of this attribute to the subnet-mask key of the network-boot-arguments PROM variable of the LDom.

Type and dimension: string-scalar

Default: ""

Gateway

During the online operation, the agent sets the value of this attribute to the router-ip key of the network-boot-arguments PROM variable of the LDom.

Type and dimension: string-scalar

Default: ""

DNS

During the online operation, the agent sets the value of this attribute to the name-servers key of the network-boot-arguments PROM variable of the LDom.

Type and dimension: string-scalar

Default: ""

RemoveLDomConfigForMigration

If enabled, the agent removes the LDom configuration from the system during offline and clean operations provided CfgFile attribute is configured. You need to enable this attribute if domain migration is planned for the logical domain. This is because domain migration cannot be performed if logical domain configuration is present on the target node for migration.

Type and dimension: boolean-scalar

Default: 0

Example: 1

DomainFailurePolicy

Specifies the list of master domains and the failure policies set for master domains that govern the behavior of VCS-managed logical domains. The key of the attribute is the name of the master domain and the value for the key of the attribute is the failure policy enacted by the master domain on the logical domain. The failure policy is enacted by the master domain in the event of loss of the master domain. The possible values for the failure policy are ignore, stop, reset, and panic. For more information on the failure policies of the master domain, refer to the ldm(1M) manual page.

By default, the DomainFailurePolicy attribute is set with master domain as 'primary' and failure policy as 'stop'.

The DomainFailurePolicy attribute need to be set to a non-default value only when the logical domain is provided with storage and network services from more than one I/O domain and the logical domain need to be made available even when the primary domain is rebooted or shut down for maintenance.

It is highly recommended to set the same failure policy for a master domain for all the LDom resources (logical domains) configured on a physical system. If the attribute is set to different failure policies for the same master domain for different LDom resources, then the agent ensures that the failure policy with the highest priority is set on the master domain. For more information on failure policy priority, see Notes for the DomainFailurePolicy attribute.

You can change the attribute value dynamically when the LDom resource is online. The LDom agent ensures that the changed failure policy is dynamically set on the master domain in the order of priority, without the need to take down the LDom resource. For more information on the behavior of this attribute, see the Notes for the DomainFailurePolicy attribute section.

DomainFailurePolicy (Continued)

Type-dimension: string-association

Default: {primary = "stop"}

Example: {primary= ignore, secondary = "stop"}. In this example, primary and secondary are the master domains from where storage and network services are exported to the logical domain.

UserName

Name of the user authorized to perform migration of the logical domain on to the host from another host.

Type and dimension: string-scalar

Default: root

Example: lmuser

Password

Specifies encrypted password for the user configured using the UserName attribute. Use one of the following commands to encrypt the password:

vcsencrypt -agent

Or

vcsencrypt -agent

Type and dimension: string-scalar

Default: None

Example: password

MigrateTimeout

The maximum time for the migrate entry point to complete migration of the logical domain after which it is terminated. The value is in seconds.

Type and dimension: integer-scalar

Default: 600

Example: 900

MigrateWaitLimit

Number of monitor intervals to wait after completing the migrate procedure and before the resource (logical domain) migrates.

Type and dimension: integer-scalar

Default: 2

Example: 4

ReregPGR

If the ReregPGR attribute is set to 1 when you live migrate the logical domain using the hagrp -migrate command, the LDom agent runs the vxdmpadm pgrrereg command inside the logical domain. This command re-registers the Persistent Group Reservation (PGR) keys after the migration is complete. To execute the vxdmpadm command, you must enable password-less SSH communication for the root user between the control domain and the logical domain.

You must set the ReregPGR attribute to 1 only when all the following parameters are met:

Type and dimension: boolean-scalar

Default: 0

Example: 0

Meter

This attribute defines the meters based on which the failover decision is taken for the service group containing the LDom resource. The keys of this attribute must be subset of intersection of HostMeters (cluster attribute) and AvailableMeters (type level). You cannot override this attribute at the resource level and you cannot modify it at run time.

Type and dimension: string-association

Default: { SCPU, SMem }

Example: { SCPU }

MeterControl

At every ForecastCycle, an extra flag is passed to the meter entry point to perform the forecasting. This flag is currently not used by the LDom agent.

Type and dimension: string-association

Default: { MeterInterval=600, ForecastCycle=0 }

MeterTimeout

The maximum time for the meter entry point to complete. The value is in seconds.

Type and dimension: integer-scalar

Default: 300

Example: 900

OnlineStableTime

The expected boot time of the LDom guest in seconds. This attribute is only applicable when the resource is under IMF monitoring.

If the LDom agent is under IMF monitoring and if it receives an user-initiated start domain event, the agent waits for the number of seconds mentioned in the OnlineStableTime attribute and then schedules the monitor cycle.

Type and dimension: integer-scalar

Default: 20

CertBasedMigration

If the value is set to 1, VCS will perform cert-based migration. If value is not set, it will perform password-based migration.

Default: 0