Sponsored Content
Top Forums UNIX for Advanced & Expert Users Clustering solution for RH Linux AS and Solaris x86/AMD 64 Post 64606 by TioTony on Tuesday 1st of March 2005 11:54:53 PM
Old 03-02-2005
Hi Izzy,
I have various levels of experience with Sun Cluster, Veritas Cluster, HACMP (IBM), Red Hat AS clusters, Tru64 clusters, and SuSe clusters.
My personal opinion (please don't turn this into an OS vs. OS string) is Sun is dying and linux is rising. That being said it may still not be time for you to jump ship yet.
Wait until RH releases the Cluster Suite and GFS for RHAS 4.0 then get a copy to play with. RHAS 4.0 includes LVM and has an LVM gui which may make it easier to transition between Veritas terminalogy and Red Hat LVM. Red Hat's LVM is very similar to HP's LVM. RHAS 3.0 has LVM but it only gives you a GUI during the install. This may or may not be a problem for you. After the install it's all command line.
I have a few clusters running OCFS and GFS. My preference from the sysadmin side is for GFS because it too contains some LVM type features that allow you to grow the size of pools dynamically. Both GFS and OCFS were tough to install and configure when they were first released but they have both gotten better. OCFS is actually pretty easy to install and configure at this point. GFS is a little more cumbersome because you have to define the fencing mechanisms, nodes, and pools. Once you figure it out it is not so bad.
The only show stopper type of gotcha I have run into with RHAS clusters, OCFS, and GFS is a bug in GFS where the first 8 characters of the hostname must be unique. This is not fixed as of GFS 6 Update 4 but RH has told me it will be fixed in the next major release (6.1?). The only way I got around this was to rename my machines.
With the Veritas cluster we had a storage compatiblity issue with our HP VA 7410. We switched the storage to a SUN T3 and got around that problem.
Other then those two issues both have been pretty stable. RH will end up being cheaper becuase you don't have to pay for Veritas. The hardware and OS costs probably won't change much from Sun.
We have multiple RHAS clusters from versions 2.1 to 4.0 with 2,3, and 4 nodes. We have several clusters running 9i RAC and 10g ASM on the same machine using ext3, RAW (and ASM managed RAW), OCFS, and GFS without a problem.

Bottom line - RHAS 3.0 was really starting to be a solid production level clustering system. RHAS 4.0 appear to be even better (but I am still waiting for cluster suite and GFS).

If anyone wants working samples of the config files for GFS just post back and I will open a new thread with them.

Thanks,
TioTony
 

9 More Discussions You Might Find Interesting

1. SuSE

Linux suse for AMD

Hi everybody I have a SLES 8 on my own desktop and now I want to install oracle on it so I should install service pack3 on it, but when I setup it my linux Os can't start up and it say "Kernel panic". My desktop's components is 1-CPU:AMD Athlon 3200+ 64bit 2-Mainboard :Asus A8N SLES... (2 Replies)
Discussion started by: hkoolivand
2 Replies

2. Solaris

Solaris 9.0 (x86 on AMD Opteron) reboots after i FTP through Telnet

Hi All, I have installed Solaris 9 on on an AMD Opteron based server. The server is rebooting after i perform the following: - Logon to Solaris 9 AMD box through telnet or putty - ftp to any other box suppose box A where the FTP server is running - After logging in to the box A through... (1 Reply)
Discussion started by: jsvarma
1 Replies

3. Solaris

Solaris on AMD 770 chipset

hi is there anyone out there who has experience with installing Solaris on this chipset? there is one entry in the HCL doc about it (BigAdmin - HCL: Gigabyte GA-MA770-DS3 rev1.0 ) but that person apparently doesnt reply when another asks him some questions. im looking to install on... (3 Replies)
Discussion started by: Landser
3 Replies

4. Red Hat

Clustering Red Hat Enterprise linux Advanced Platform 5.2 (x86-64 bit)

Hello Professionals, We have high-end HP rack servers. We need to provide application fail-over for business continuity. We have done benchmarking of the application on RHEL 5.2 on HP servers to estimate the hardware requirement so as to meet next 3-5 years business growth. Presently we... (1 Reply)
Discussion started by: kgayyar
1 Replies

5. Solaris

Sample solution for Firefox-3.6.10 pkg in solaris 10 for X86

download pkg from sunfreeware web site (root user mode) step1: #mkdir opt/sft step2: download the package and save it in the opt/sft directory step3: #bunzip2 firefox-3.6.10.en-US.solaris-10-fcs-i386-pkg.bz2 step 4 #pkgadd -d ./firefox-3.6.10.en-US.solaris-10-fcs-i386-pkg ... (3 Replies)
Discussion started by: alamin2010
3 Replies

6. UNIX for Dummies Questions & Answers

Linux Clustering

hi guys Some time ago I used Linux HA(Heartbeat) to setup like 3 cluster. Now I have to install another 2 cluster and was checking more info to be sure HA was still used but I found some other stuff like OpenAIS - Corosync - Pacemaker to tell you the truth I am kinda confused here I get... (0 Replies)
Discussion started by: karlochacon
0 Replies

7. Linux

Linux os clustering

Hi, I have done the OS clustering in linux redhat 5.6, my one node is down and when i am trying to reboot the other node it is not coming up. any pointer to this would be helpful. the SAN storage luns are not coming as mounted (2 Replies)
Discussion started by: mohitj.engg
2 Replies

8. Ubuntu

Newbie With Linux Clustering, Need Help!!

Hi All, I am new user here and a new one to try clustering with Ubuntu nodes, and need help. If I should be in another place please mention. I have a two nodes with Ubuntu 14.04 installed on them. I need to make a cluster consisting of these two nodes with purpose of experimentation with... (3 Replies)
Discussion started by: IncognitoExpert
3 Replies

9. Solaris

Is it safe to install x86 Solaris 10 U6 after installed-Linux-and-FreeBSD?

I've installed Slack 14.2 on /dev/sda1 (/dev/sda2 is swap) and FreeBSD 12 on /dev/sda3 and lilo is the boot manager. FreeBSD slices are as follows; / on /dev/ada0S3a, swap on /dev/ada0s3e, /var on /dev/ada0s3b, /tmp on /dev/ada0s3d and /usr on /dev/ada0s3f. I hesitate to install Solaris 10... (2 Replies)
Discussion started by: vectrum
2 Replies
Intro(9S)						    Data Structures for Drivers 						 Intro(9S)

NAME
Intro, intro - introduction to kernel data structures and properties DESCRIPTION
Section 9P describes kernel properties used by device drivers. Section 9S describes the data structures used by drivers to share informa- tion between the driver and the kernel. See Intro(9E) for an overview of device driver interfaces. In Section 9S, reference pages contain the following headings: o NAME summarizes the purpose of the structure or property. o SYNOPSIS lists the include file that defines the structure or property. o INTERFACE LEVEL describes any architecture dependencies. o DESCRIPTION provides general information about the structure or property. o STRUCTURE MEMBERS lists all accessible structure members (for Section 9S). o SEE ALSO gives sources for further information. Of the preceding headings, Section 9P reference pages contain the NAME, DESCRIPTION, and SEE ALSO fields. Every driver MUST include <sys/ddi.h> and <sys/sunddi.h>, in that order, and as final entries. The following table summarizes the STREAMS structures described in Section 9S. +-----------------------------+-----------------------------+ | Structure | Type | +-----------------------------+-----------------------------+ |copyreq |DDI/DKI | +-----------------------------+-----------------------------+ |copyresp |DDI/DKI | +-----------------------------+-----------------------------+ |datab |DDI/DKI | +-----------------------------+-----------------------------+ |fmodsw |Solaris DDI | +-----------------------------+-----------------------------+ |free_rtn |DDI/DKI | +-----------------------------+-----------------------------+ |iocblk |DDI/DKI | +-----------------------------+-----------------------------+ |linkblk |DDI/DKI | +-----------------------------+-----------------------------+ |module_info |DDI/DKI | +-----------------------------+-----------------------------+ |msgb |DDI/DKI | +-----------------------------+-----------------------------+ |qband |DDI/DKI | +-----------------------------+-----------------------------+ |qinit |DDI/DKI | +-----------------------------+-----------------------------+ |queclass |Solaris DDI | +-----------------------------+-----------------------------+ |queue |DDI/DKI | +-----------------------------+-----------------------------+ |streamtab |DDI/DKI | +-----------------------------+-----------------------------+ |stroptions |DDI/DKI | +-----------------------------+-----------------------------+ The following table summarizes structures that are not specific to STREAMS I/O. +-----------------------------+-----------------------------+ | Structure | Type | +-----------------------------+-----------------------------+ |aio_req |Solaris DDI | +-----------------------------+-----------------------------+ |buf |DDI/DKI | +-----------------------------+-----------------------------+ |cb_ops |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_device_acc_attr |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_dma_attr |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_dma_cookie |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_dma_lim_sparc |Solaris SPARC DDI | +-----------------------------+-----------------------------+ |ddi_dma_lim_x86 |Solaris x86 DDI | +-----------------------------+-----------------------------+ |ddi_dma_req |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_dmae_req |Solaris x86 DDI | +-----------------------------+-----------------------------+ |ddi_idevice_cookie |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_mapdev_ctl |Solaris DDI | +-----------------------------+-----------------------------+ |devmap_callback_ctl |Solaris DDI | +-----------------------------+-----------------------------+ |dev_ops |Solaris DDI | +-----------------------------+-----------------------------+ |iovec |DDI/DKI | +-----------------------------+-----------------------------+ |kstat |Solaris DDI | +-----------------------------+-----------------------------+ |kstat_intr |Solaris DDI | +-----------------------------+-----------------------------+ |kstat_io |Solaris DDI | +-----------------------------+-----------------------------+ |kstat_named |Solaris DDI | +-----------------------------+-----------------------------+ |map |DDI/DKI | +-----------------------------+-----------------------------+ |modldrv |Solaris DDI | +-----------------------------+-----------------------------+ |modlinkage |Solaris DDI | +-----------------------------+-----------------------------+ |modlstrmod |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_address |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_arq_status |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_device |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_extended_sense |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_hba_tran |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_inquiry |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_pkt |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_status |Solaris DDI | +-----------------------------+-----------------------------+ |uio |DDI/DKI | +-----------------------------+-----------------------------+ SEE ALSO
Intro(9E) NOTES
Do not declare arrays of structures as the size of the structures can change between releases. Rely only on the structure members listed in this chapter and not on unlisted members or the position of a member in a structure. SunOS 5.11 15 May 2001 Intro(9S)
All times are GMT -4. The time now is 08:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy