Sponsored Content
Operating Systems Solaris Solaris Cluster Device Problem Post 302987367 by sonofsunra on Thursday 8th of December 2016 12:08:36 PM
Old 12-08-2016
Thank you for your reply Peasant.

For the document, it is just suits me, because I am using also old version of cluster and solaris (cluser 3.3 and sol10) for my environment.

I used solaris volum manager for FS. I m guessing that most probably I had this issue because of that but I want to be sure. DukeNuke2's document using zfs for it. Now I ll start over and I will try zfs. I am wonderig that do I have same problem with zfs or not.
I used svm because svm support global file system. now I ll try zfs.

And also after that I ll look for the ISCSI protocol for virtualbox environment.

I ll share my exprience in here.

Thank you again.
 

4 More Discussions You Might Find Interesting

1. 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

2. High Performance Computing

Solaris 10 - Cluster Problem

Hi, I am trying to install Solaris cluster with Solaris10 and Cluster suite 3.2 2/08. After going through customer configuration in "scinstall" utility, I am facing a problem. At the time of selecting 2nd node's file system type, I am giving input as /globaldevices which is very much part of... (9 Replies)
Discussion started by: hi2joshi
9 Replies

3. Solaris

Solaris cluster scdidadm Inquiry on device failed.

Solaris 10, Solaris Cluser 3.2, two node cluster, all software installed succefully, all nodes join to the cluster And on snod2 didn't recognize disks as a did devices and I can't make a quorum device. snod1#/usr/cluster/bin/cluster status === Cluster Nodes === --- Node Status --- Node... (2 Replies)
Discussion started by: Uran
2 Replies

4. Red Hat

PaceMaker Cluster Fence Device

I have 2 VM's setup with a shared VMware disk running RHEL 7.1 (just updated to 7.2 with yum update), and would like to know what is the easiest Fence device to implement for testing purposes. Apparently, I need a fence device before my IP resources will come online. I have the cluster... (1 Reply)
Discussion started by: mrmurdock
1 Replies
scconf_dg_svm(1M)					  System Administration Commands					 scconf_dg_svm(1M)

NAME
scconf_dg_svm - change Solaris Volume Manager device group configuration. SYNOPSIS
scconf -c -D [generic_options] DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page. A Solaris Volume Manager device group is defined by a name, the nodes upon which this group can be accessed, a global list of devices in the disk set, and a set of properties used to control actions such as potential primary preference and failback behavior. For Solaris Volume Manager device groups, only one disk set can be assigned to a device group, and the group name must always match the name of the disk set itself. In Solaris Volume Manager, a multihosted or shared device is a grouping of two or more hosts and disk drives that are accessible by all hosts, and that have the same device names on all hosts. This identical device naming requirement is achieved by using the raw disk devices to form the disk set. The device ID pseudo driver (DID) allows multihosted devices to have consistent names across the cluster. Only hosts already configured as part of a disk set itself can be configured into the nodelist of a Solaris Volume Manager device group. At the time drives are added to a shared disk set, they must not belong to any other shared disk set. The Solaris Volume Manager metaset command creates the disk set, which also initially creates and registers it as a Solaris Volume Manager device group. Next, you must use the scconf command to set the node preference list, the preferenced, failback and numsecondaries subop- tions. If you want to change the order of node preference list or the failback mode, you must specify all the nodes that currently exist in the device group in the nodelist. In addition, if you are changing the order of node preference, you must also set the preferenced suboption to true. If you do not specify the preferenced suboption with the "change" form of the command, the already established true or false setting is used. You cannot use the scconf command to remove the Solaris Volume Manager device group from the cluster configuration. Use the Solaris Volume Manager metaset command instead. You remove a device group by removing the Solaris Volume Manager disk set. OPTIONS
See scconf(1M) for the list of supported generic options. See metaset(1M) for the list of metaset related commands to create and remove disk sets and device groups. Only one action option is allowed in the command. The following action options are supported. -c Change the ordering of the node preference list, change preference and failback policy, and change the desired number of secondaries. EXAMPLES
Example 1 Creating and Registering a Disk Set The following metaset commands create the disk set disksetand register the disk set as a Solaris Volume Manager device group. Next, the scconf command is used to specify the order of the potential primary nodes for the device group, change the preferenced and fail- back options, and change the desired number of secondaries. host1# metaset -s diskset1 -a -h host1 host2 host1# scconf -c -D name=diskset1,nodelist=host2:host1, preferenced=true,failback=disabled,numsecondaries=1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevicegroup(1CL), scconf(1M), metaset(1M) Sun Cluster 3.2 10 Jul 2006 scconf_dg_svm(1M)
All times are GMT -4. The time now is 03:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy