Products/HA/DellRedHatHALinuxCluster/Cluster - Revision history

Vvaldez at 22:53, 24 April 2009

2009-04-24T22:53:51Z

← Older revision		Revision as of 22:53, 24 April 2009
Line 1:		Line 1:
-	<font size=1>[[~~../../~~../../DellRedHatHALinuxCluster\|Dell\|Red Hat HA Linux]] > Cluster</font>	+	<font size=1>[[../../DellRedHatHALinuxCluster\|Dell\|Red Hat HA Linux]] > Cluster</font>

	=Configuring Your Cluster=		=Configuring Your Cluster=
Line 526:		Line 526:

	----		----
-	<font size=1>[[~~../../~~../../DellRedHatHALinuxCluster\|Dell\|Red Hat HA Linux]] > Cluster</font>	+	<font size=1>[[../../DellRedHatHALinuxCluster\|Dell\|Red Hat HA Linux]] > Cluster</font>

Vvaldez at 22:52, 24 April 2009

2009-04-24T22:52:57Z

← Older revision		Revision as of 22:52, 24 April 2009
Line 1:		Line 1:
-	<font size=1>[[~~Products~~/HA/DellRedHatHALinuxCluster\|Dell\|Red Hat HA Linux]] > Cluster</font>	+	<font size=1>[[../../../../DellRedHatHALinuxCluster\|Dell\|Red Hat HA Linux]] > Cluster</font>

	=Configuring Your Cluster=		=Configuring Your Cluster=
Line 522:		Line 522:
	<br>5. After you successfully fence one node, repeat this process for the second		<br>5. After you successfully fence one node, repeat this process for the second
	node.		node.
		+
		+
		+
		+	----
		+	<font size=1>[[../../../../DellRedHatHALinuxCluster\|Dell\|Red Hat HA Linux]] > Cluster</font>

Vvaldez: /* Configure DRAC CMC Fencing */

2009-04-23T20:32:49Z

Configure DRAC CMC Fencing

← Older revision		Revision as of 20:32, 23 April 2009
Line 123:		Line 123:
	PowerEdge M1000e Chassis Management Controller (CMC) acts as a network power switch of sorts. You configure a single IP address on the CMC, and connect to that IP for management. Individual blade slots can be powered up or down as needed. At this time Conga does not have an entry for the Dell CMC when configuring fencing. The steps in this section describe how to manually configure fencing for the Dell CMC. See [https://bugzilla.redhat.com/show_bug.cgi?id=496724 Bug 496724] for details on Conga support.		PowerEdge M1000e Chassis Management Controller (CMC) acts as a network power switch of sorts. You configure a single IP address on the CMC, and connect to that IP for management. Individual blade slots can be powered up or down as needed. At this time Conga does not have an entry for the Dell CMC when configuring fencing. The steps in this section describe how to manually configure fencing for the Dell CMC. See [https://bugzilla.redhat.com/show_bug.cgi?id=496724 Bug 496724] for details on Conga support.

-	'''NOTE''': At the time of this writing, there is a bug that prevents the CMC from powering up the blade after it is fenced. To recover from a fenced outage, manually ~~powerup~~ the blade (or connect to the CMC and issue the command '''racadm serveraction -m server-# powerup'''). New code available for testing can correct this behavior. See [https://bugzilla.redhat.com/show_bug.cgi?id=466788 Bug 466788] for beta code and further discussions on this issue.	+	'''NOTE''': At the time of this writing, there is a bug that prevents the CMC from powering the blade back up after it is fenced. To recover from a fenced outage, manually power the blade on (or connect to the CMC and issue the command '''racadm serveraction -m server-# powerup'''). New code available for testing can correct this behavior. See [https://bugzilla.redhat.com/show_bug.cgi?id=466788 Bug 466788] for beta code and further discussions on this issue.

	'''NOTE''': Using the individual iDRAC on each Dell Blade is not supported at this time. Instead use the Dell CMC as described in this section. If desired, you may configure IPMI as your secondary fencing method for individual Dell Blades. For information on support of the Dell iDRAC, see [https://bugzilla.redhat.com/show_bug.cgi?id=496748 Bug 496748].		'''NOTE''': Using the individual iDRAC on each Dell Blade is not supported at this time. Instead use the Dell CMC as described in this section. If desired, you may configure IPMI as your secondary fencing method for individual Dell Blades. For information on support of the Dell iDRAC, see [https://bugzilla.redhat.com/show_bug.cgi?id=496748 Bug 496748].

Vvaldez: /* Configure DRAC SSH Fencing */

2009-04-23T20:31:18Z

Configure DRAC SSH Fencing

← Older revision		Revision as of 20:31, 23 April 2009
Line 156:		Line 156:
	=====Configure DRAC SSH Fencing=====		=====Configure DRAC SSH Fencing=====
	By default any DRAC5/iDRAC/iDRAC6 has SSH enabled, but telnet disabled.		By default any DRAC5/iDRAC/iDRAC6 has SSH enabled, but telnet disabled.
-	To use DRAC5/iDRAC/iDRAC6 fencing over SSH check the '''Use SSH ~~(DRAC5 only)~~''' option while adding fencing device to a node. ~~In order for fencing over SSH to work, luci with version~~ '''>=0.12.1-7.3.el5_3~~''' is required~~.	+	To use DRAC5/iDRAC/iDRAC6 fencing over SSH check the '''Use SSH''' option while adding a fencing device to a node.
		+	<br>'''NOTE''': This SSH option in Conga is included with <tt>luci-0.12.1-7.3.el5_3</tt> and greater.

	====Update Cluster Configuration====		====Update Cluster Configuration====

Vvaldez: /* Creating Your Cluster Using Conga */

2009-04-23T15:20:47Z

Creating Your Cluster Using Conga

← Older revision		Revision as of 15:20, 23 April 2009
Line 57:		Line 57:
	https://{management_node_hostname_or_IP_address}:8084		https://{management_node_hostname_or_IP_address}:8084
	Where {''management_node_hostname_or_IP_address''} is the hostname or IP address of the management server running <tt>luci</tt>.		Where {''management_node_hostname_or_IP_address''} is the hostname or IP address of the management server running <tt>luci</tt>.
-	<br>'''NOTE''': If you encounter any errors, see section "Troubleshooting Conga".	+	<br>'''NOTE''': If you encounter any errors, see section [[#Troubleshooting Conga\|Troubleshooting Conga]].
	<br>2. Enter your username and password to securely log in to the luci server.		<br>2. Enter your username and password to securely log in to the luci server.
	<br>3. Go to the cluster tab.		<br>3. Go to the cluster tab.

Vvaldez at 20:42, 22 April 2009

2009-04-22T20:42:22Z

Show changes

Rhentosh: added breadcrumb to top of page

2008-09-12T20:04:35Z

added breadcrumb to top of page

← Older revision		Revision as of 20:04, 12 September 2008
Line 1:		Line 1:
		+	<font size=1>[[Products/HA/DellRedHatHALinuxCluster\|Dell\|Red Hat HA Linux]] > [[Products/HA/DellRedHatHALinuxCluster/Cluster\|Cluster]]</font>
		+
	=Configuring Your Cluster=		=Configuring Your Cluster=
	This section discusses how to install and configure Red Hat Cluster Suite and Global File System on your Dell\|Red Hat HA Cluster system using Conga and CLI tools.		This section discusses how to install and configure Red Hat Cluster Suite and Global File System on your Dell\|Red Hat HA Cluster system using Conga and CLI tools.

Rhentosh: /* Example Configuration of NFS */

2008-06-13T21:40:34Z

Example Configuration of NFS

← Older revision		Revision as of 21:40, 13 June 2008
Line 350:		Line 350:
	2. Click '''Services''' and enter a service name.		2. Click '''Services''' and enter a service name.
	<br>3. Select a recovery policy.		<br>3. Select a recovery policy.
-	<br>4. Click '''Add~~'''~~ a resource to this service.	+	<br>4. Click '''Add a resource to this service'''.
	<br>5. From the drop-down menu, choose '''Use an existing global resource'''.		<br>5. From the drop-down menu, choose '''Use an existing global resource'''.
	<br>6. Select the resource IP Address that you created in step 1.		<br>6. Select the resource IP Address that you created in step 1.

Rhentosh: /* Managing the Cluster Infrastructure from the CLI */

2008-06-13T21:20:22Z

Managing the Cluster Infrastructure from the CLI

← Older revision		Revision as of 21:20, 13 June 2008
Line 296:		Line 296:

	===Managing the Cluster Infrastructure from the CLI===		===Managing the Cluster Infrastructure from the CLI===
-	~~The proper procedure for starting and stoping~~ the ~~cluster infrastructure from the cli is outlined below. Note that these~~ commands ~~need to be executed~~ on ~~each node. It is best to run these commands as close~~ to ~~parallel as possible.~~	+	Run each of the following commands concurrently on all nodes to start the cluster:
-		+
-	~~Staring~~ the cluster ~~infrastructure~~:	+
	[root]# service cman start		[root]# service cman start
	[root]# service clvmd start		[root]# service clvmd start
Line 304:		Line 302:
	[root]# service rgmanager start		[root]# service rgmanager start

-	~~Stopping~~ the cluster ~~infrastructure~~:	+	Run each of the following commands concurrently on all nodes to stop the cluster:
	[root]# service rgmanager stop		[root]# service rgmanager stop
		+	[root]# service gfs stop
	[root]# service clvmd stop		[root]# service clvmd stop
-	~~[root]# service gfs stop~~
	[root]# service cman stop		[root]# service cman stop

Rhentosh: /* Creating Global File System with CLI Tools */

2008-06-13T21:08:30Z

Creating Global File System with CLI Tools

← Older revision		Revision as of 21:08, 13 June 2008
Line 258:		Line 258:
	** {gfs filesystem name}—A unique identifier among GFS file systems.		** {gfs filesystem name}—A unique identifier among GFS file systems.
	** {number of journals}—One journal per node is required. However, at least one additional journal is recommended.		** {number of journals}—One journal per node is required. However, at least one additional journal is recommended.
-	** {name of clustered logical volume}—The cluster logical volume that you created. For example ''/dev/vg_cluster/~~clustered/lv~~''.	+	** {name of clustered logical volume}—The cluster logical volume that you created. For example ''/dev/vg_cluster/lv_cluster''.

	To create a file system:		To create a file system:
	<br>1. From one system only execute the following command:		<br>1. From one system only execute the following command:
-	[root@node1 ~]# gfs_mkfs -t {cluster name}:{gfs filesystem name} -p lock_dlm -j {number of ~~journales~~} {name of clustered logical volume}	+	[root@node1 ~]# gfs_mkfs -t {cluster name}:{gfs filesystem name} -p lock_dlm -j {number of journals} {name of clustered logical volume}

	For example:		For example: