2001-01-02 -+- Jim Dennis -+- jimd@starshine.org -+- It's a pity this article is riddled with so many typos and grammatical
errors. It actually made it difficult to read in places.

I would be nice if there were good information about Linux support for multi-initiator ("shared") SCSI. I haven't found any. There are
references (a Google search will reveal that much). However, none of
them provides enough information for a typical or senior sysadmin to
make a decision: Will it work? Should I recommend it? How would I do it?

It seems that FC (fibre channel) and the SANS that people are building
around it are going to accomplish the same things that people were trying
to do with M-I SCSI. Apparently there have traditionally been device
driver and even hardware microcode problems that make multi-initiator
SCSI difficult and that constrain the range of hardware that can be
used in such a setup. (The author of this article mentions the fact
that some SCSI hosts don't offer an option to change their own ID
--- the can only be SCSI ID 7. That's just one problem; they must also
allow the system to skip the bus reset! Otherwise any initiator/system
on the SCSI chain that was rebooted would reset the whole bus. Clearly
the (Linux) device driver must also refrain from gratuitous resets. It's
not clear that all of the Linux SCSI drivers could be used in an M-I
cluster).

2001-11-04 -+- Sandeep Banerjee -+- sandeep_b@email.com -+- Hi Atif,

Your page proved to be a good starting point for my search on redundancy. I am looking for some non-commercial solution for system level redundancy - the objective being host switchover on any process or OS failure.

I need a simple solution that does not require RAID or any kind of checkpointing or backup. All it should do is to monitor the health of the system, and switch over at the slightest hint of failure to the backup host. Note that there are only 2 hosts.

I look forward to some guidance from you in this regard.

Regards,
Sandeep

Bangalore, India. 2001-11-27 -+- Witzbold -+- -+- dies ist ein test und kann gelöscht werden 2002-02-03 -+- Allen Stewart -+- -+- This article is a good starting point for HA but it seems the technologies listed are still not mature and it will be years before the number of IP failover clusters and stateful failover clusters are even a drop in the bucket vs Windows 2000 based HA systems.

Allen 2002-02-27 -+- Ghazanfer -+- falkenn@hotmail.com -+- Hi! Atif.
ur article gave good insides of HA. but i also wanted to know that, do v really want 2 NIC's and a serial connection? Can't it be done using one NIC on each machine. 2002-03-07 -+- zhanghai -+- jordan_zhang@dell.com -+- Hi Atif

I am appreciate you share your experence about cluster and SAN. It’s just what I had in mind.I hope you can offer detail configuration about GFS. I want to know if you have non-commercial and similarity software.I am looking for your feedback

Jordan 2002-04-11 -+- Bernd Tannenbaum -+- tannenbaum@itenos.de -+- Hi all :)

----Problems with 2 Servers and 1 Router (Arp-Table)----

At first, i have to say i`m new to linux but now got the job of clustering 2 Apache-webserver.
I found Heartbeat but am not happy with it. 90% of the possible errors in the network result in a disconnection of the server from the internet. (Reasons could be a single switchport going down or a network cable accidently removed by the wrong people.) In this case Heartbeat would do nothing because the slave still reaches his Master and will not take over the resource.
In a second try i did not configure the failover with a second network card but configured it with the standard eth0. Now the slave noticed when the Master was unreachable, took the resource and sended a garp to tell the router that he now has the Web-server-IP. But when the Master comes back (maybe because the Switchport that was down reinitialized) it still has the resource, too. In fact, he never gave it up. The Slave notices now that the master is back and gives up the resource, so the Master is the only owner again. But because the Master thinks he never has lost the resource he doesnt send the garp. So the router doesnt know the new owner of the Resource-IP and the webserver is down.
I implemented some cronjobs on both servers to do what heartbeat doesnt do:
Testing the Gateway, then testing the Server-IP and sending Garps.
They work fine, but i feel that a professional programm written by people who know a lot more about linux-cluster than me should be able to do the same.
Maybe someone can help me out?

With best regards,
Bernd Tannenbaum 2002-07-09 -+- Frederick L. Belfon -+- fredericksec@yahoo.com -+- I would like to know how to configure a 2 node high availability cluster for an apache webserver that makes use of an MySQL database.

I am new to Linux and need some real ehlp

Thank you -+- 136.148.1.94 = Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) 2003-02-27 -+- richard clason -+- richard@firstdirectsolutions.co.uk -+- Can anyone suggest how to set up the following. To run a server using Red Hat, Ensim, PHP, MqSQL, E-mail and SSL. Should this server fail a second server to cut in and take over all traffic. Both servers would have upto data data.

Thanks -+- 80.195.20.133 = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705) #2003-05-28 -+- Kiran -+- kirank@ece.iisc.ernet.in -+- Hi,

Does HA serves when the service on primary is dead? I mean if httpd on
clustnode1 is not running(but clustnode1 is up and reachable), will
clustnode2 take over from clustnode1?

Please mention how to achieve this.

Thanks
Kiran -+- 144.16.64.4 = Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10smp i686) 2003-07-30 -+- amol -+- amolbhore@yahoo.com -+- I want information regarding the failure of the backup node
in the cluster computing, i dont know whether MPICH take care
of it or we have to take care of it explicitly -+- 203.197.93.66 = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) #2003-09-30 -+- Milan -+- konik2@orngemail.sk -+- Hello my tape retained in recorder after stoping play (by remote control )
how can I get it back - In need to return it tomorrow to store... -+- 193.81.246.12 = Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)