In a message dated: Fri, 14 Jul 2000 17:20:05 EDT
[EMAIL PROTECTED] said:
>Are you sure? The Heartbeat documentation show configurations over
>serial as well as ethernet. I was thinking of a senario where I install
>a fourth network card in the systems and link them with a crossover cable,
>and link them with a serial line, or possibly two serial lines.
You can do heartbeat either over serial or ethernet. I don't think you can do
both simultaneously, but I might be wrong. You could easily dedicate an IP
connection, but if your ethernet I/O gets bogged down, it's going to affect
both the heartbeat link and your network, it's all the same IP stack.
>This seems ok to me. I like
>the idea of shared disk storage, but it seems like overkill for a simple
>ipchains firewall. I don't mind if I'm writing a firewall log to a
>separate hard disk. Also there is a watchdog driver available which in
>the event of the heartbeat going dead for say a minute, will reboot the
>system. This would prevent the machine from regaining it's heartbeat
>after it is pronounced dead.
The shared disk isn't necessarilly for shared storage, though it would allow
you to do this. More importantly it's for "disk pinging heartbeat". I.e.,
the systems ping each other over the shared scsi bus via the disk.
You only need something like a 10MB partition for this, so you could easily
store all you're firewall scripts, etc. on a different partition.
Kimberlite may seem like overkill compared to heartbeat, but I'd rather go
overboard than have to drive into my site at 03:00 to switch the firewall
over! The amount of money you spend on this won't be that significant, a 9GB
scsi drive is <$200. A couple of scsi controllers and some cables, another
$200. It's worth it if I don't have get up at 03:00 :)
--
Seeya,
Paul
----
"I always explain our company via interpretive dance.
I meet lots of interesting people that way."
Niall Kavanagh, 10 April, 2000
If you're not having fun, you're not doing it right!
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
