sun Cluster resource group cant failover


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications High Performance Computing sun Cluster resource group cant failover
# 15  
Old 07-09-2008
Hi,


can you please confirm what is it exactly that I need to do as I am not sure?

how is this done :
if your cluster is 3.2 you should not use Network_resources_used any more, just place your logical host in the dependency list
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Process to add mount point in Sun Cluster existing HAplus resource

Hi Well I would like to know step by step process of adding a mountpoint in HAPLUS resource in SUN cluster as I go the below command to add a mount point but not the step by step process of adding a mount point in existing HA Plus resource. clrs set -p FileSystemMountPoints+=<new_MP>... (3 Replies)
Discussion started by: amity
3 Replies

2. Red Hat

Linux Cluster failover issue

Hi Guys, I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me. How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Discussion started by: munna529
2 Replies

3. Solaris

Solaris Cluster Failover based on scan rate

Dear Experts, If there is a possible Solaris Cluster failover to second node based on scan rate? I need the documentation If solaris cluster can do this. Thank You in Advance Edy (3 Replies)
Discussion started by: edydsuranta
3 Replies

4. Solaris

Sun cluster 4.0 - zone cluster failover doubt

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)
Discussion started by: NVA
0 Replies

5. AIX

Adding a Volume Group to an HACMP Resource Group?

Hi, I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over) Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 Replies

6. Gentoo

How to failover the cluster ?

How to failover the cluster ? GNU/Linux By which command, My Linux version 2008 x86_64 x86_64 x86_64 GNU/Linux What are the prerequisites we need to take while failover ? if any Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies

7. AIX

Resource Group Monitoring

Hi, I have a requirement to monitor the HACMP Resource Groups. At present in my environment, if the Resource Groups fail over from preferred node to Secondary node we dont get notification. Can some one help me in creating a scrript. I have more than one RG online. (Max 4 Resource Groups in... (2 Replies)
Discussion started by: srnagu
2 Replies

8. Solaris

Sun Cluster 3.1 failover

Hi, We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover? Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies

9. High Performance Computing

Veritas Cluster Server Management Console IP Failover

I have just completed a first RTFM of "Veritas Cluster Server Management Console Implementation Guide" 5.1, with a view to assessing it to possibly make our working lives easier. Unfortunately, at my organisation, getting a test installation would be worse than pulling teeth, so I can't just go... (2 Replies)
Discussion started by: Beast Of Bodmin
2 Replies

10. HP-UX

ServiceGuard cluster & volume group failover

I have a 2-node ServiceGuard cluster. One of the cluster packages has a volume group assigned to it. When I fail the package over to the other node, the volume group does not come up automatically on the other node. I have to manually do a "vgchange -a y vgname" on the node before the package... (5 Replies)
Discussion started by: Wotan31
5 Replies
Login or Register to Ask a Question
scha_cluster_get(1HA)					       Sun Cluster Commands					     scha_cluster_get(1HA)

NAME
scha_cluster_get - access cluster information SYNOPSIS
scha_cluster_get -O optag [args] DESCRIPTION
The scha_cluster_get command accesses and generates information about a cluster. You can access information about the cluster, nodes, zones, host names, resource groups, resource types, and states. The command is intended for use in shell script implementations of callback methods for resource types. These callback methods for resource types represent services that are controlled by the cluster's Resource Group Manager (RGM). This command provides the same information as the scha_resource_get() function. This command sends output to the standard output (stdout) in formatted strings on separate lines, as described in the scha_cmds(1HA) man page. You can store the output in shell variables. You can also parse the output with shell commands such as the awk command. OPTIONS
The following options are supported: -O optag The optag argument indicates the information to be accessed. Depending on the optag, an additional argument may be needed to indicate the cluster node or zone for which information is to be retrieved. Note - optag options, such as NODENAME_LOCAL and NODENAME_NODEID, are not case sensitive. You can use any combination of uppercase and lowercase letters when you specify optag options. The following optag values are supported: ALL_NODEIDS Generates on successive lines the numeric node identifiers of all nodes in the cluster. ALL_NODENAMES Generates on successive lines the names of all nodes in the cluster. ALL_NONGLOBAL_ZONES Generates on successive lines the nodename:zonename string of all the non-global zones on all nodes in the cluster. ALL_NONGLOBAL_ZONES_NODEID Generates on successive lines the nodename:zonename string of all non-global zones on the cluster node whose numeric node identifier is given as the argument. ALL_PRIVATELINK_HOSTNAMES Generates on successive lines the host names by which all cluster nodes are addressed on the cluster interconnect. ALL_RESOURCEGROUPS Generates on successive lines the names of all the resource groups that are being managed in the cluster. ALL_RESOURCETYPES Generates on successive lines the names of all the resource types that are registered in the cluster. ALL_ZONES Generates on successive lines the nodename:zonename string of all zones, including the global zone, on all nodes in the cluster. ALL_ZONES_NODEID Generates on successive lines the nodename:zonename string of all zones, including the global zone, on the cluster node whose numeric node identifier is given as the argument. CLUSTERNAME Generates the name of the cluster. NODEID_LOCAL Generates the numeric node identifier for the node where the command is executed. NODEID_NODENAME Generates the numeric node identifier of the node indicated by the name. Requires an additional unflagged argument that is the name of a cluster node. NODENAME_LOCAL Generates the name of the cluster node where the command is executed. NODENAME_NODEID Generates the name of the cluster node indicated by the numeric identifier. Requires an additional unflagged argu- ment that is a numeric cluster node identifier. NODESTATE_LOCAL Generates UP or DOWN depending on the state of the node where the command is executed. NODESTATE_NODE Generates UP or DOWN depending on the state of the named node. Requires an additional unflagged argument that is the name of a cluster node. PRIVATELINK_HOSTNAME_LOCAL Generates the host name by which the node on which the command is run is addressed over the cluster interconnect. PRIVATELINK_HOSTNAME_NODE Generates the host name by which the named node is addressed on the cluster interconnect. Requires an additional unflagged argument that is the name of a cluster node. SYSLOG_FACILITY Generates the number of the syslog(3C) facility that the RGM uses for log messages. The value is 24, which corre- sponds to the daemon facility. You can use this value as the facility level in the logger(1) command to log mes- sages in the cluster log. ZONE_LOCAL Generates the name of the zone from which the command is issued. The format of the zone name that is returned is nodename:zonename. EXAMPLES
Example 1 Using the scha_cluster Command in a Shell Script The following shell script uses the scha_cluster command to print whether each cluster node is up or down: #!/bin/sh nodenames=`scha_cluster_get -O All_Nodenames` for node in $nodenames do state=`scha_cluster_get -O NodeState_Node $node` printf "State of node: %sexit: %dvalue: %s0 "$node" $? "$state" done EXIT STATUS
The following exit status codes are returned: 0 Successful completion. nonzero An error occurred. Error codes are described in 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), logger(1), sh(1), scha_cmds(1HA), syslog(3C), scha_calls(3HA), scha_cluster_get(3HA), attributes(5) Sun Cluster 3.2 6 Sep 2006 scha_cluster_get(1HA)