Tuning the Sun Cluster HA for BroadVision One-To-One Enterprise Fault Monitor

The Sun Cluster HA for BroadVision One-To-One Enterprise fault monitor checks the health of the BroadVision One-To-One Enterprise back-end and Interaction Manager processes. The health of these processes impacts the failure history of the BroadVision One-To-One Enterprise resources, which in turn drives the fault monitor's actions. For each BroadVision One-To-One Enterprise resource, fault monitor actions include no action, restart, or failover.

The Sun Cluster HA for BroadVision One-To-One Enterprise fault monitor is contained in a resource whose resource type is SUNW.bv.

System properties and extension properties of the resource control the behavior of the fault monitor. The default values of these properties determine the preset behavior of the fault monitor. The preset behavior should be suitable for most Sun Cluster installations. Therefore, you should tune the Sun Cluster HA for BroadVision One-To-One Enterprise fault monitor only if you need to modify this preset behavior.

Tuning the Sun Cluster HA for BroadVision One-To-One Enterprise fault monitor involves the following tasks:

• Setting the interval between fault monitor probes

• Setting the timeout for fault monitor probes

• Defining the criteria for persistent faults

• Specifying the failover behavior of a resource

Information about the Sun Cluster HA for BroadVision One-To-One Enterprise fault monitor that you need to perform these tasks is provided in the subsections that follow.

Tune the Sun Cluster HA for BroadVision One-To-One Enterprise fault monitor when you register and configure Sun Cluster HA for BroadVision One-To-One Enterprise. For more information, see Registering and Configuring Sun Cluster HA for BroadVision One-To-One Enterprise.

For detailed information, see “Tuning Fault Monitors for Sun Cluster Data Services” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

Operation of the Interaction Manager Fault Monitoring

For Interaction Manager resources, failover happens only when both of the following conditions are met.

• The value of the desired primaries is less than the value of the maximum primaries.

• One of the nodes is unavailable.

After failover, the fault monitor will not restart the resource on any cluster node if both of the following conditions occur.

• The values of the maximum primaries and desired primaries of the Interaction Manager resource group are the same.

• The fault monitor has completed restarting the Interaction Manager resource the number of times that the Retry_count property specifies.

Operation of the Fault Monitor Probes

The fault monitors for each BroadVision One-To-One Enterprise resource (root host, back-end host, and Interaction Manager host) monitor the following processes.

• The orbix daemon (orbixd), which is common for all of the BroadVision One-To-One Enterprise resources – The probes use the ps(1) command to ensure that orbixd is functioning. If orbixd is not functioning, the probe considers the failure as complete, and the Resource Group Manager (RGM) restarts the orbix daemon.

  The orbix daemon is started with the checkpoint feature. Therefore, the BroadVision One-To-One Enterprise servers, which the previous instance of orbixd started, continue to run with the new instance of orbixd.

• The BroadVision One-To-One Enterprise daemons that you have configured in the resource – If orbixd is healthy, the probe uses the BroadVision command bvconf ps to ensure that the BroadVision One-To-One Enterprise daemons are functioning. If BroadVision One-To-One Enterprise daemons are not functioning, the RGM restarts the resource, which restarts all of the configured daemons.