I have installed sun cluster 3.2 on two sprac servers. Configured a failover resource group. Added a LogicalHostname resource to it. LogicalHostname is also added to /etc/hosts with ip address.
I am able to access cluster by share ip used for logical hostname but when i try to switch the resource to other node of cluster, the resource go offline on both node and never switch.
Hi All,
I was asked to Switch the service from failover to active node as we need to reboot active node for regular maintenance. Unfortunately our senior admin left the organization. It would be helpful if some one answer this query. Detailed info with steps will be appreciated.
Here are... (1 Reply)
Hello everyone,
I have two Solaris 10 servers that are on cluster. The cluster is a Sun Cluster 3.2
I have a script cronned that stop/start a ressource in a resource group everyday.
Today I have checked the status of the ressources and I found that my ressource group have a "Error--stop... (1 Reply)
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
I am using VMware Workstation-7 on Windows-XP host .
I am trying to configure Solaris 10-X86 guest os based 2 nodes Sun Cluster .
I have added one extra Virtual Lan adapter on my VMware with another subnet (that I would like to put for SUN Cluster private communication).
I have... (0 Replies)
Any body can tell me where i can download sun cluster installation and configuration video.
is there any option to install cluster in 32 bit virtual machine.
please help (4 Replies)
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Hi All
I hav working knowledge on solarois 10.
Could anyone suggest me any doc or material for learning SUN cluster from scratch. Anything from basic level .
Thanks in advance!! (1 Reply)
Hi,
I am getting these messages constantly at random times there is not visible impact but would like to know what these messages mean?
Cluster.RGM.rgmd: resource group
on node change to RG_ON_PENDING_R_RERT
Cluster.RGM.rgmd: resource group on node change to RG_ONLINE (1 Reply)
scha_resourcegroup_get(1HA) Sun Cluster Commands scha_resourcegroup_get(1HA)NAME
scha_resourcegroup_get - access resource group information
SYNOPSIS
scha_resourcegroup_get -O optag -G group [args]
DESCRIPTION
The scha_resourcegroup_get command accesses information about a resource group that is under the control of the Resource Group Manager
(RGM) cluster facility.
This command is intended to be used in shell script implementations of the callback methods for resource types. These resource types repre-
sent services that are controlled by the cluster's RGM. This command provides the same information as the scha_resourcegroup_get(3HA) C
function.
Information is generated by the command to standard output (stdout) in formatted strings as described in scha_cmds(1HA). The output is a
string or several strings on separate lines. The output can be stored in shell variables and parsed using shell facilities or awk(1) for
further use by the script.
You need solaris.cluster.resource.read role-based access control (RBAC) authorization to use this command. See rbac(5).
You must also be able to assume a role to which the Sun Cluster Commands rights profile has been assigned to use this command. Authorized
users can issue privileged Sun Cluster commands on the command line from the pfsh(1), pfcsh(1), or pfksh(1) profile shell. A profile shell
is a special kind of shell that enables you to access privileged Sun Cluster commands that are assigned to the Sun Cluster Commands rights
profile. A profile shell is launched when you run su(1M) to assume a role. You can also use pfexec(1) to issue privileged Sun Cluster com-
mands.
OPTIONS
The following options are supported:
-G group Name of the resource group.
-O optag Specifies the information that is to be accessed. Depending on the optag that you specify, you might need to include an addi-
tional operand to indicate the node or zone for which information is to be retrieved.
Note -
optag values, such as DESIRED_PRIMARIES and FAILBACK, are not case sensitive. You can use any combination of uppercase and
lowercase letters when you specify optag options.
The following optag values retrieve the corresponding resource group properties. The value of the named property of the
resource group is generated. The RG_STATE property refers to the value on the particular node or zone where the command is
executed.
AUTO_START_ON_NEW_CLUSTER
DESIRED_PRIMARIES
FAILBACK
GLOBAL_RESOURCES_USED
IMPLICIT_NETWORK_DEPENDENCIES
MAXIMUM_PRIMARIES
NODELIST
PATHPREFIX
PINGPONG_INTERVAL
RESOURCE_LIST
RG_AFFINITIES
RG_DEPENDENCIES
RG_DESCRIPTION
RG_IS_FROZEN
RG_MODE
RG_PROJECT_NAME
RG_SLM_TYPE
RG_SLM_PSET_TYPE
RG_SLM_CPU
RG_SLM_CPU_MIN
RG_STATE
RG_STATE_NODE
RG_SYSTEM
SUSPEND_AUTOMATIC_RECOVERY
Note -
RG_STATE_NODE requires an unflagged argument that specifies a node or zone. This optag value generates the value of the resource group's
RG_STATE property for the specified node or zone. If the unflagged argument specifies a non-global zone, the format is nodename:zonename.
EXAMPLES
Example 1 A Sample Script Using scha_resourcegroup_get
The following script is passed a -G argument, which provides the required resource group name. Next, the scha_resourcegroup_get command is
used to get the list of resources in the resource group.
#!/bin/sh
while getopts G: opt
do
case $opt in
G) group="$OPTARG";;
esac
done
resource_list=`scha_resourcegroup_get -O Resource_list -G $group`
for resource in $resource_list
do
printf "Group: %s contains resource: %s0 "$group" "$resource"
done
EXIT STATUS
The following exit status codes are returned:
0 The command completed successfully.
nonzero An error occurred.
Failure error codes are described scha_calls(3HA).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscdev |
+-----------------------------+-----------------------------+
|Interface Stability |Stable |
+-----------------------------+-----------------------------+
SEE ALSO awk(1), scha_cmds(1HA), scha_calls(3HA), scha_resourcegroup_get(3HA), attributes(5), rg_properties(5), rbac(5)Sun Cluster 3.2 6 Sep 2006 scha_resourcegroup_get(1HA)