Contents of an SC_CALLBACK_REG Message (Sun Cluster 3.1 10/03 Data Services Developer's Guide)

Sun Cluster 3.1 10/03 Data Services Developer's Guide

Contents of an `SC_CALLBACK_REG` Message

Each ADD_CLIENT, ADD_EVENTS, and REMOVE_EVENTS message contains a list of events. The following table describes the event types that the CRNP accepts, including the required name and value pairs.

If a client either:

Sends a REMOVE_EVENTS message that specifies one or more event types for which the client has not previously registered, or
Registers for the same event type twice

the server silently ignores these messages.

Class and Subclass	Name and Value Pairs	Description
`EC_Cluster` `ESC_cluster_membership`	Required: none Optional: none	Registers for all cluster membership change events (node death or join)
`EC_Cluster` `ESC_cluster_rg_state`	One required, as follows: `rg_name` Value type: string Optional: none	Registers for all state change events for resource group `name`
`EC_Cluster` `ESC_cluster_r_state`	One required, as follows: `r_name` Value type: string Optional: none	Registers for all state change events for resource `name`
`EC_Cluster` None	Required: none Optional: none	Registers for all Sun Cluster events

Class and Subclass

Name and Value Pairs

Description

EC_Cluster

ESC_cluster_membership

Required: none

Optional: none

Registers for all cluster membership change events (node death or join)

EC_Cluster

ESC_cluster_rg_state

One required, as follows:

rg_name

Value type: string

Optional: none

Registers for all state change events for resource group name

EC_Cluster

ESC_cluster_r_state

One required, as follows:

r_name

Value type: string

Optional: none

Registers for all state change events for resource name

EC_Cluster

None

Required: none

Optional: none

Registers for all Sun Cluster events