InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - Solaris

Notes for the DomainFailurePolicy attribute

When the DomainFailurePolicy attribute is set, the LDom agent sets the master domain of the logical domain with the key of the attribute and the value of the key as the failure policy of the master domain.

The LDom agent uses the following command to set the master for the logical domain:

# ldm set-domain master=master-domain guestldom

The LDom agent uses the following command to set the failure policy for the master domain:

# ldm set-domain failure-policy=failure-policy master-domain

As the DomainFailurePolicy attribute is available at the resource level, you can set the failure policy of the master domain to different values for different LDom resource knowingly or unknowingly. However, at any given point, the LDom agent can set only one failure policy for the master domain. In a cluster with multiple LDom resources, different values for the failure policy of the master domain can create a conflict. To avoid such a conflict, the LDom agent uses internal priority while setting the failure policy of the master domain.

The internal priority is as follows:

If the failure policy of the master domain is set to a lower priority on the system than the one set in the LDom resource for the DomainFailurePolicy attribute, then the failure policy of the master domain is changed to the value in the attribute.

If the failure policy of the master domain is set to a higher priority on the system than the one set in the LDom resource for the DomainFailurePolicy attribute, then the failure policy of the master domain will not be changed to the value in the attribute. The LDom agent logs a message to indicate the conflict for the first time.

If the failure policy of the master domain is set to ignore, then the LDom agent does not add the master domain to the master list of the logical domain. If the master domain is already part of the masters list of the logical domain, the LDom agent removes the master domain from the masters list.

Example 1

Failure policy of the master domain (primary) is set to ignore on the system and the DomainFailurePolicy attribute for the LDom resource is changed to { primary = "stop" }. To check whether the failure policy of the master domain (primary) is set to ignore on the system, enter the following command:

# ldm list-bindings primary | grep failure-policy

In this example, as the internal priority of the LDom agent is assigned to stop and as it is higher than ignore, the failure policy of the primary domain is changed to stop. The LDom agent uses the following command to change the failure policy of the primary domain to stop:

# ldm set-domain failure-policy=stop primary

Example 2

Failure policy of the master domain (primary) is set to panic on the system and the DomainFailurePolicy attribute for the LDom resource is changed to { primary = "stop" }. To check whether the failure policy of the master domain (primary) is set to panic on the system, enter the following command:

# ldm list-bindings primary | grep failure-policy

In this example, as the internal priority of the LDom agent is assigned to stop and as it is lower than panic, the failure policy of the primary domain is retained as panic.

If the failure policy of a master domain need to be set to a value of lower priority than the value currently set on the system, you must manually execute the ldm command. The LDom agent uses the following command to change the failure policy of the primary domain to stop from reset or panic:

# ldm set-domain failure-policy=stop primary

Example 3

If the value of the failure policy of the master domain is specified as ignore in the DomainFailurePolicy attribute, then the master domain is excluded from the masters list of the logical domain by the LDom agent.

If the masters list of a logical domain contains primary and secondary and if the DomainFailurePolicy attribute of the LDom resource for the logical domain is changed to {primary = ignore, secondary = "stop" }, then the primary domain is removed from the masters list of the logical domain.

Before you change the DomainFailurePolicy attribute, you can enter the following command to check whether the masters list of a logical domain contains primary and secondary:

# ldm list-bindings guestldom | grep master

The following output shows that the logical domain contains both primary and secondary:

master=primary, secondary

After you change the DomainFailurePolicy attribute, you can enter the following command to check whether the primary domain is removed from the masters list of the logical domain.

# ldm list-bindings guestldom | grep master

The following output shows that the primary domain is removed from the masters list:

master= secondary

For use case scenarios and for VCS configuration where the DomainFailurePolicy attribute must be set, refer to the InfoScale Virtualization Guide.