Switching services from active node to failovernode in cluster
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 the below details. I need to reboot lab1 and need to switch all services to lab2 or lab3.
I believe the /appfs is related to cluster. I'm bit rusty with cluster administration
Please help!!!
Code:
#hostname
lab2
#clustat
Member Name Status
------ ---- ------
lab1-int Online, rgmanager
lab2-int Online, Local, rgmanager
lab3-int Online, rgmanager
Service Name Owner (Last) State
------- ---- ----- ------ -----
app_gfs_svc lab2-int started
app_prod lab1-int started
app_test (lab1-int) disabled
app_upgrade (none) disabled
# df -TPH /appfs
Filesystem Type Size Used Avail Use% Mounted on
/dev/dm-50 gfs 32G 24G 8.3G 75% /appfs
Last edited by Scrutinizer; 03-20-2016 at 12:05 PM..
Reason: code tags
Hello,
Under ksh I have to run a script on one of the nodes of a Solaris 8 cluster which at some time must execute a command on the alternate node:
# rsh <name> "command"
I have to implement this script on all the clusters of my company (a lot of...).
Fortunately, the names of the two nodes... (11 Replies)
My apologies in advance if this question has already been asked or if I use incorrect terminology; I have tried searching for nearly an hour without any luck.
Is there any way to change the active TTY for a session? I was monitoring a long (~5 hour) process through an SSH connection and the... (4 Replies)
Hi,
Please advise me whereas I have two node cluster server configured with MC/SG. Application and DB are running on Node 1, while Node 2 is standby.
All the volume group devices are part of cluster environment. There is only one package running at node 1.
Node 2 is having the problem to... (1 Reply)
hi,
i am trying to setup a 2 node cluster environment. following is what i have;
1. 2 x sun ultra60 - 450MHz procs, 1GB RAM, 9GB HDD, solaris 10
2. 2 x HBA cards
3. 2 x Connection leads to connect ultra60 with D1000
4. 1 x D1000 storage box.
5. 3 x 9GB HDD + 2 x 36GB HDD
first of all,... (1 Reply)
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
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... (0 Replies)
Setting up HACMP 6.1 on a two node cluster. The other node works fine and can start properly on STABLE state (VGs varied, FS mounted, Service IP aliased). However, the other node is always stuck on ST_JOINING state. Its taking forever and you can't stop the cluster as well or recover from script... (2 Replies)
Discussion started by: depam
2 Replies
LEARN ABOUT HPUX
cmrunnode
cmrunnode(1m)cmrunnode(1m)NAME
cmrunnode - run a node in a high availability cluster
SYNOPSIS
cmrunnode [-v] [node_name...] [-t | -w none]
DESCRIPTION
cmrunnode causes a node to start its cluster daemon to join the existing cluster. This command verifies the network configuration before
causing the node to start its cluster daemon.
To start a cluster on one of its nodes, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the clus-
ter configuration file. See access policy in cmquerycl(1m).
Starting a node will not cause any active packages to be moved to the new node. However, if a package is DOWN, has its switching enabled,
and is able to run on the new node, that package will automatically run there.
If node_name is not specified, the cluster daemon will be started on the local node and will join the existing cluster.
Options
cmrunnode supports the following options:
-v Verbose output will be displayed.
-t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. The -w
option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet
any external dependencies such as EMS resources, package subnets, and storage.
node_name...
Start the cluster daemon on the specified node(s).
-w none
By default network probing is performed to check that the network connectivity is the same as when the cluster was configured.
Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should
only be used if this network configuration is known to be correct from a recent check.
RETURN VALUE
cmrunnode returns the following value:
0 Successful completion.
1 Command failed.
EXAMPLES
Run the cluster daemon on the current node:
cmrunnode
Run the cluster daemons on node1 and node2:
cmrunnode node1 node2
AUTHOR
cmrunnode was developed by HP.
SEE ALSO cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmruncl(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmrunnode(1m)
03-20-2016
Switching services from active node to failovernode in cluster
