12-08-2016
Most important part is to use ISCSI protocol instead of shared virtualbox devices.
Get a box to act as ISCSI target, while your cluster nodes are initiators.
This is your disk subsystem from which your will make failover zpools or metasets.
Also the document is outdated for current releases, you might want to keep that in mind.
Once you have ISCSI setup done, you can just follow the regular documentation for your release keeping mind of iscsi notes if existing.
Hope that helps
Best regards
Peasant.
4 More Discussions You Might Find Interesting
1. High Performance Computing
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
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 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
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
LEARN ABOUT REDHAT
iscsi.conf
ISCSI.CONF(5) File Formats Manual ISCSI.CONF(5)
NAME
iscsi.conf - iSCSI Target and LUN configuration
SYNOPSIS
/etc/iscsi.conf
DESCRIPTION
This manual page describes the format of the /etc/iscsi.conf file. This file is a simple text file that iscsid(8) uses to locate iSCSI tar-
get devices and LUNs. Comments are marked by lines beginning with '#'.
Available entries include:
DiscoveryAddress=<address>
IP address or hostname to use for target discovery. A TCP port number may be specified by appending a colon followed by the port
number. This entry must start in the first column, and must not contain any whitespace.
TargetIpAddr=<address>
A synonym for DiscoveryAddress.
Username=<user>
Specify the authentication user. If this entry precedes all DiscoveryAddress entries, it serves as the default. If this entry is
indented under a DiscoveryAddress entry, it specifies the user for all targets discovered at that IP address.
Password=<pass>
Specify the authentication password for the previously listed iSCSI If this entry precedes all DiscoveryAddress entries, it serves
as the default. If this entry is indented under a DiscoveryAddress entry, it specifies the user for all targets discovered at that
IP address.
EXAMPLE
# set the default user and password
Username=alice
Password=nty57nbe
# targets at this address will use the default Username and Password
DiscoveryAddress=192.168.10.94
# targets at this address will use the Username and Password below
DiscoveryAddress=192.168.10.95
Username=beatrice
Password=93fdgc20
NOTES
The iSCSI initiator drivers, README files, and example configuration files are available on the Linux-iSCSI homepage at:
http://linux-iscsi.sourceforge.com <http://linux-iscsi.sourceforge.com>
FILES
/etc/iscsi.conf
iSCSI Target and LUN configuration
SEE ALSO
iscsid(8)
$Revision: 1.9 $ $Date: 2002/09/19 20:00:32 $ ISCSI.CONF(5)