Sponsored Content
Operating Systems Solaris What is the procedure to reboot cluster nodes Post 302580735 by garskoci on Friday 9th of December 2011 12:00:13 PM
Old 12-09-2011
Take a look at the
Code:
hastop

command.

I don't know what clstop does. But, if you want to offline all of the servicegroups and shutdown the cluster you can run
Code:
hastop -all

Or, run
Code:
hastop -local

on each node. If you add a
Code:
-force

to it, only the cluster will shut down. The servicegroup will remain online. But, I don't think that you wan that.

Not knowing your cluster configuration, I would think that you would want to run
Code:
hastop -local

on each cluster node to let VCS offline the servicegroups. You will need to know what's controled by VCS and what's not. I see many times that Oracle RAC is outside of the cluster. Then you might have a DBA shut down RAC.
 

10 More Discussions You Might Find Interesting

1. High Performance Computing

Bonding, IP alias, Virtual IP, 2 nodes cluster

Hi ! I have a simple setup of 2 PC (with linux Red-Hat) where the first PC is the primary machine and the second the backup. I use DRBD for data replication and Red-Hat cluster suite for HA (High Availability). I have tested both. Now I NEED a COMMON IP ADDRESS (or Master/unique IP address) for... (0 Replies)
Discussion started by: Danny Gilbert
0 Replies

2. UNIX for Dummies Questions & Answers

IP Alias, Bonding or Virtual IP, 2 nodes Cluster, which one to use ?

Hi ! I have a simple setup of 2 PC (with linux Red-Hat) where the first PC is the primary machine and the second the backup. I use DRBD for data replication and Red-Hat cluster suite for HA (High Availability). I have tested both. Now I NEED a COMMON IP ADDRESS (or Master/unique IP address) for... (3 Replies)
Discussion started by: Danny Gilbert
3 Replies

3. Emergency UNIX and Linux Support

Rebooting 3 to 1 Cluster nodes.

hello Gurus, My current set up is 3 to 1 Cluster (SUN Cluster 3.2) running oracle database. Task is to reboot the servers. My query is about the procedure to do the same. My understanding is suspend the databases to avoid switchover. Then execute the command scshutdown to down the cluster... (4 Replies)
Discussion started by: EmbedUX
4 Replies

4. Red Hat

Centos/rhel 5 cluster 3 nodes with out Quorum

Hi all, i have 3 nodes cluster (Centos 5 cluster suit) with out quorum disk, node vote = 1, the value of a quorum = 2, when 2 nodes going offline, cluster services are destoys. How i can save the cluster and all services(move all services to one alive node) with out quorum disk when other... (3 Replies)
Discussion started by: Flomaster
3 Replies

5. Solaris

Need advise on setting up solaris 10 2 nodes cluster

I am new to setting up sun solaris 10 cluster, I have 2 sun sparc t3-1 servers (identical), going to use them as web servers (sun one java web server 7), looking for data replication and real time fail over. My question is do I need external storage to configure the cluster? or I can just use... (3 Replies)
Discussion started by: spitfire2011
3 Replies

6. Red Hat

How to troubleshoot a 1000 nodes Apache cluster?

Hi all. May I get some expert advice on troubleshooting performance issues of a 1000 nodes Apache LB cluster. Users report slow loading/response of webpages. Different websites are hosted on this cluster for different clients. But all are reporting the same issue. Could you please let me know... (1 Reply)
Discussion started by: admin_xor
1 Replies

7. AIX

Re-cluster 2 HACMP 5.2 nodes

Hi, A customer I'm supporting once upon a time broke their 2 cluster node database servers so they could use the 2nd standby node for something else. Now sometime later they want to bring the 2nd node back into the cluster for resilance. Problem is there are now 3 VG's that have been set-up... (1 Reply)
Discussion started by: elcounto
1 Replies

8. UNIX for Advanced & Expert Users

Arbitrator for 2 nodes ocfs cluster

Is there any way to create a arbitrary node for ocfs2 on a virtual machine (others are physical servers) so it won't go panic when one of physical server goes down? This is for load balanced application servers. Any setting example or tips? Thanks. (0 Replies)
Discussion started by: malayo
0 Replies

9. Red Hat

RedHat Cluster: Nodes won't see each other

Hi All; I try to build a Redhat Cluster (CentOS 6) on vmware. But each node sees the other down like: # clustat Cluster Status for mycluster @ Wed Apr 8 11:01:38 2015 Member Status: Quorate Member Name ID Status ------ ---- ... (0 Replies)
Discussion started by: Meacham12
0 Replies

10. Red Hat

RedHat Cluster: Nodes won't see each other

Hi All; I try to build a Redhat Cluster (CentOS 6) on vmware. But each node sees the other down like: # clustat Cluster Status for mycluster @ Wed Apr 8 11:01:38 2015 Member Status: Quorate Member Name ID Status ------ ---- ... (1 Reply)
Discussion started by: Meacham12
1 Replies
clvxvm(1CL)						 Sun Cluster Maintenance Commands					       clvxvm(1CL)

NAME
clvxvm - configure VERITAS Volume Manager for Sun Cluster SYNOPSIS
/usr/cluster/bin/clvxvm -V /usr/cluster/bin/clvxvm [subcommand] -? /usr/cluster/bin/clvxvm subcommand -v /usr/cluster/bin/clvxvm encapsulate /usr/cluster/bin/clvxvm initialize DESCRIPTION
The clvxvm utility initializes VERITAS Volume Manager (VxVM) on a Sun Cluster node and optionally performs root-disk encapsulation. There is no short form of this command name. You can only use this utility with VxVM versions 4.1 or later. For older versions of VxVM, instead use the scvxinstall(1M) utility. The general form of this command is as follows: clvxvm [subcommand] [options] You can omit subcommand only if options specifies the -? option or the -V option. Each option of this command has a long form and a short form. Both forms of each option are given with the description of the option in the OPTIONS section of this man page. You can only use this command from a node that is booted in cluster mode. All nodes in the cluster configuration must be current cluster members. All nodes must be added to the node authentication list. You can use this command only in the global zone. SUBCOMMANDS
The following subcommands are supported: encapsulate Encapsulates the root disk and performs other Sun Cluster-specific tasks. The encapsulate subcommand performs the following tasks: o Verifies that the current node is booted in cluster mode and that all other cluster nodes are running in cluster mode. o Verifies that the user is superuser. o Enforces a cluster-wide value for the vxio major number by modifying the node's /etc/name_to_major file, if necessary. This task ensures that the vxio number is the same on all cluster nodes. o Runs several VxVM commands to prepare for root-disk encapsulation. o Modifies the global-devices entry in the /etc/vfstab file that is specified for the /global/.devices/node@n file system, where n is the node ID number. The clvxvm utility replaces the existing device path /dev/did/{r}dsk with /dev/{r}dsk. This change ensures that VxVM recognizes that the global-devices file system resides on the root disk. o Twice reboots each node that is running clvxvm. The first reboot allows VxVM to complete the encapsulation process. The sec- ond reboot resumes normal operation. The clvxvm utility includes a synchronization mechanism to ensure that the utility reboots only one node at a time, to prevent loss of quorum. o Unmounts the global-devices file system. The file system is automatically remounted after the encapsulation process is com- plete. o Recreates the special files for the root-disk volumes with a unique minor number on each node. This subcommand expects that VxVM packages and licenses are already installed and that the VxVM configuration daemon is successfully enabled on this node. Each root disk that you encapsulate must have at least two free (unassigned) partitions. Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. initialize Initializes VxVM and performs other Sun Cluster-specific tasks. The initialize subcommand performs the following tasks: o Verifies that the current node is booted in cluster mode and that all other cluster nodes are running in cluster mode. o Verifies that the user is superuser. o Enforces a cluster-wide value for the vxio major number by modifying the node's /etc/name_to_major file, if necessary. This task ensures that the vxio number is the same on all cluster nodes. o Instructs the user to reboot the node to resume operation with the new vxio major number in effect, in case the number had to be changed. This subcommand expects that VxVM packages and licenses are already installed and that the VxVM configuration daemon is successfully enabled on this node. Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. OPTIONS
The following options are supported: -? ---help Displays help information. You can use this option either alone or with a subcommand. o If you use this option alone, the list of available subcommands is printed. o If you use this option with a subcommand, the usage options for that subcommand are printed. When you use this option, no other processing is performed. -V ---version Displays the version of the command. Do not specify this option with subcommands, operands, or other options. The subcommands, operands, or other options are ignored. The -V option only displays the version of the command. No other operations are performed. -v ---verbose Displays verbose information to standard output. You can use this option with any form of the command. OPERANDS
No form of this command accepts an operand. EXIT STATUS
The complete set of exit status codes for all commands in this command set are listed on the Intro(1CL) man page. This command returns the following exit status codes: 0 CL_NOERR No error 1 CL_ENOMEM Not enough swap space 3 CL_EINVAL Invalid argument 6 CL_EACCESS Permission denied 35 CL_EIO I/O error EXAMPLES
Example 1 Initializing VxVM on a Cluster Node The following example shows how to initialize VxVM the cluster node from which the command is issued. # clvxvm initialize Example 2 Initializing VxVM on a Cluster Node and Encapsulating the Root Disk The following example shows how to initialize VxVM and encapsulate the root disk on the cluster node from which the command is issued. # clvxvm encapsulate ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ FILES
/var/cluster/cmvxvm/* Location of temporary files that are used by the clvxvm utility. /var/cluster/logs/install/clvxvm.log.pid Log file that is created by the scvxinstall utility. SEE ALSO
Intro(1CL), cldevice(1CL), cldevicegroup(1CL), clsetup(1CL), cluster(1CL), scinstall(1M), scvxinstall(1M), rbac(5) Sun Cluster Software Installation Guide for Solaris OS NOTES
The superuser can run any forms of this command. Any user can also run this command with the following options: o -? (help) option o -V (version) option To run this command with other subcommands, users other than superuser require RBAC authorizations. See the following table. +------------+---------------------------------------------------------+ |Subcommand | RBAC Authorization | +------------+---------------------------------------------------------+ |encapsulate | solaris.cluster.modify | +------------+---------------------------------------------------------+ |initialize | solaris.cluster.modify | +------------+---------------------------------------------------------+ Sun Cluster 3.2 19 Jul 2006 clvxvm(1CL)
All times are GMT -4. The time now is 02:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy