Sponsored Content
Full Discussion: Solaris 10 - Cluster Problem
Special Forums UNIX and Linux Applications High Performance Computing Solaris 10 - Cluster Problem Post 302247676 by incredible on Thursday 16th of October 2008 07:35:07 AM
Old 10-16-2008
/globaldevices (or the underlying device) has to be cluster unique. So each
cluster node has to use a different meta device.
Check that the hostnames are in both the /etc/hosts /etc/inet/ipnodes files in both nodes. Be sure you don't have some unprintable character in vfstab .
Try to get the install log from the system and post its messages
 

7 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Solaris and Cluster Patches

Simple question: After applying a cluster patch to a sun solaris box I am left with a root volume 81% full. I could run through the hassle of resizing the slices which is way too much work for a Ultra 5 running DNS only. Is there a way to clean up the /var/sadm/pkg area, aka dump the save info. (5 Replies)
Discussion started by: edkung
5 Replies

2. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. High Performance Computing

Sun Solaris cluster

Hi all, I need ur help plz how sun cluster work and i need good reference for that. ur cooperate is appreciated (4 Replies)
Discussion started by: AshAdmin
4 Replies

4. Solaris

Solaris Cluster

Hi All, i have 2 zone 1- Oracle DB Primary Server 2- Oracle DB Secondary Server i make script do r sync between this 2 zones but i am planning to do is make Solaris cluster between this zones if the primary Server field the secondary server up and running automatically without any... (1 Reply)
Discussion started by: jamisux
1 Replies

5. Solaris

SVM metaset on 2 node Solaris cluster storage replicated to non-clustered Solaris node

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

6. Solaris

Solaris Cluster Device Problem

I build up two node cluster (node1, node2) in virtualbox. For these two nodes I add 5 shared disk. (Also each node have own OS disk). 1 shared disk for vtoc 2 shared disk for NFS resource group 2 shared disk for WEB resource group When I finished my work; two nodes was ok and shared disk... (4 Replies)
Discussion started by: sonofsunra
4 Replies

7. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
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 06:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy